Allow DB connection specification via components#3222
Merged
sgoggins merged 1 commit intoaugurlabs:mainfrom Jul 10, 2025
Merged
Allow DB connection specification via components#3222sgoggins merged 1 commit intoaugurlabs:mainfrom
sgoggins merged 1 commit intoaugurlabs:mainfrom
Conversation
Require individual DB config vars when AUGUR_DB is not set and construct AUGUR_DB from them. This allows specifying username, database name, etc. separately if desired. This was added because the postgres operator provides these individually, and by accepting the individual components, the postgres operator's secret can be directly mapped to the env vars on Kubernetes/OpenShift environments. Signed-off-by: John Strunk <jstrunk@redhat.com>
sgoggins
approved these changes
Jul 9, 2025
Collaborator
sgoggins
left a comment
There was a problem hiding this comment.
Thank you! Any step towards Kubernetes is a good one!
Ulincsys
approved these changes
Jul 9, 2025
This file contains hidden or 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
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.
Description
This provides an additional method for specifying the DB connection information.
A user may now (instead of using the current
AUGUR_DBconnection string) specify the various connection string components separately:AUGUR_DB_HOST,AUGUR_DB_USER,AUGUR_DB_PASSWORD,AUGUR_DB_NAMEThis change was made to support integration with the Postgres operator in Kubernetes environments. The operator handles these connection settings as separate fields within a Secret, and by allowing Augur to accept them individually, those Secret fields can be directly mapped into the Augur container.