Skip to content

Allow DB connection specification via components#3222

Merged
sgoggins merged 1 commit intoaugurlabs:mainfrom
JohnStrunk:db-var
Jul 10, 2025
Merged

Allow DB connection specification via components#3222
sgoggins merged 1 commit intoaugurlabs:mainfrom
JohnStrunk:db-var

Conversation

@JohnStrunk
Copy link
Copy Markdown
Contributor

Description
This provides an additional method for specifying the DB connection information.

A user may now (instead of using the current AUGUR_DB connection string) specify the various connection string components separately: AUGUR_DB_HOST, AUGUR_DB_USER, AUGUR_DB_PASSWORD, AUGUR_DB_NAME

This 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.

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>
Copy link
Copy Markdown
Collaborator

@sgoggins sgoggins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Any step towards Kubernetes is a good one!

@sgoggins sgoggins merged commit 45d03f2 into augurlabs:main Jul 10, 2025
10 checks passed
@JohnStrunk JohnStrunk deleted the db-var branch July 11, 2025 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants