Closed speedythesnail closed 1 month ago
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.
Your contribution is greatly appreciated!
An easier way to reproduce:
helm template bitnami/gitea --version 2.3.11 --set postgresql.enabled=false --set externalDatabase.existingSecret=gitea-passwords
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.
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.
Name and Version
bitnami/gitea 2.3.6
What architecture are you using?
amd64
What steps will reproduce the bug?
Empty Secret Manifest:
Pod Manifest:
Are you using any custom parameters or values?
custom-values.yaml
What is the expected behavior?
The externaldb secret should not be created if specifying an existing secret
What do you see instead?
A blank externaldb secret is created.
Additional information
I am working on a PR right now that will fix this bug by applying the same logic to the externaldb-secret creation as is done on the secrets creation.
I am creating this issue so I can have a reference for the PR when it is ready.