add postgresql.existingHost & existingSecret for backend's SECRETKEY #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…KEY and allow setting an existingHost for the database Signed-off-by: Toni Tauro <[email protected]>
Signed-off-by: Toni Tauro <[email protected]>
eyenx
changed the title
eyenx
changed the title
eyenx
changed the title
MitanOmar
approved these changes
Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add an existingSecret for the SECREKEY and allow setting an existingHost for the database
This change will make it possible to deploy caluma on Production (There we have DBaaS)
What I also saw and needs fixing is the initDBScripts which are potentially not run anymore due to the update to the newest postgresql Version. I'll create an issue for it.