-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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.
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
[bitnami/pgbouncer] Make env var POSTGRESQL_PASSWORD
optional, of config is mounted
#63802
Comments
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Hi, how's it going |
POSTGRESQL_PASSWORD
optional, of config is mountedPOSTGRESQL_PASSWORD
optional, of config is mounted
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Not stale. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
I have the same issue unfortunately. Workaround so far has been to specify POSTGRESQL_USERNAME, POSTGRESQL_PASSWORD and POSTGRESQL_HOST otherwise pgbouncer won't start - whilst also adding |
Name and Version
bitnami/pgbouncer:1.22
What is the problem this feature will solve?
If somebody wants to use the option of mounting a volume with configuration files into
/bitnami/pgbouncer/conf/
, they still need to define the env varPOSTGRESQL_PASSWORD
.The value of this env var is not used, but the container will not start without it.
What is the feature you are proposing to solve the problem?
It would be nice, if the container would start without the env var being present. Assuming, that a configuration file is mounted.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: