Skip to content

Conversation

@JohnStrunk
Copy link
Member

Description

  • This changes the test for the DB connection components to not exit with failure if AUGUR_DB can't be constructed.

Fixes #3225

This changes the test for the DB connection components to not exit with
failure if AUGUR_DB can't be constructed.

Signed-off-by: John Strunk <jstrunk@redhat.com>
Copy link
Contributor

@MoralCode MoralCode left a comment

Choose a reason for hiding this comment

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

I am able to podman run with these changes

$ podman run -it --rm augur-new:latest bash
root@43ce7fefc860:/augur# 

LGTM

Copy link
Member

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

LGTM!

echo -e "When AUGUR_DB is not set, you must set AUGUR_DB_HOST, AUGUR_DB_USER,\nAUGUR_DB_PASSWORD, and AUGUR_DB_NAME"
exit 1
# If AUGUR_DB is not set, check for individual environment variables and construct AUGUR_DB connection string
if [[ -n "$AUGUR_DB_HOST" ]] && [[ -n "$AUGUR_DB_USER" ]] && [[ -n "$AUGUR_DB_PASSWORD" ]] && [[ -n "$AUGUR_DB_NAME" ]]; then
Copy link
Member

Choose a reason for hiding this comment

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

Got it!

@sgoggins sgoggins merged commit 06d0c7a into chaoss:main Jul 14, 2025
10 checks passed
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.

Debugging via docker/podman run requires database credentials

3 participants