Skip to content

Comments

Chart: Allow setting an existing secret for PgBouncer config#15296

Merged
kaxil merged 4 commits intoapache:masterfrom
DerekHeldtWerle:feature/existing-pgbouncer-secret
Apr 10, 2021
Merged

Chart: Allow setting an existing secret for PgBouncer config#15296
kaxil merged 4 commits intoapache:masterfrom
DerekHeldtWerle:feature/existing-pgbouncer-secret

Conversation

@DerekHeldtWerle
Copy link
Contributor

Previously, if a user wanted to supply the username and password to the users.txt secret for use by pgbouncer, they had to be set directly in the values.yaml file. This change allows users to create this secret out of band (with the pgbouncer.ini) and avoid supplying secrets directly.

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
pgbouncerConfigSecretName: ~
configSecretName: ~

Since it is already in pgbouncer key -- adding pgbouncer is a bit redundant. Can you also give an example of an existing config with pgbouncer.ini and users.txt

@DerekHeldtWerle DerekHeldtWerle requested a review from kaxil April 9, 2021 01:08
@kaxil
Copy link
Member

kaxil commented Apr 9, 2021

Can you rebase on latest master and fix the conflicting files please @DerekHeldtWerle

@DerekHeldtWerle DerekHeldtWerle force-pushed the feature/existing-pgbouncer-secret branch from 7dea237 to 6874f89 Compare April 9, 2021 21:29
@DerekHeldtWerle
Copy link
Contributor Author

@kaxil Done 👍

@kaxil kaxil changed the title adds pgbouncerConfigSecretName to allow the setting of an existing secret for pgbouncers config Chart: Allow setting an existing secret for PgBouncer config Apr 9, 2021
@kaxil kaxil merged commit d5ea9fe into apache:master Apr 10, 2021
@DerekHeldtWerle DerekHeldtWerle deleted the feature/existing-pgbouncer-secret branch April 11, 2021 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants