Skip to content

test(8.9): honor RDBMS_POSTGRESQL_USERNAME for the role in postgresql-cluster fixture #6310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eamonnmoloney wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −1
Open

test(8.9): honor RDBMS_POSTGRESQL_USERNAME for the role in postgresql-cluster fixture #6310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .../camunda-platform-8.9/test/integration/scenarios/common/resources/postgresql-cluster.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,15 @@ metadata:
namespace: $NAMESPACE
spec:
instances: 1
# The login role derives from $RDBMS_POSTGRESQL_USERNAME so it stays
# self-consistent with the JDBC user the chart connects as (rdbms values +
# the psql-create-db job both use $RDBMS_POSTGRESQL_USERNAME). Previously the
# role was hardcoded `app`, so any value other than `app` failed with
# "password authentication failed for user ...". In CI the var is `app`, so
# this renders identically.
Comment on lines +22 to +23
managed:
roles:
- name: app
- name: $RDBMS_POSTGRESQL_USERNAME
ensure: present
superuser: true
login: true
Expand Down
Loading