We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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/redmine 32.0.1
amd64
In the values.yaml https://github.com/bitnami/charts/blob/main/bitnami/redmine/values.yaml#L141C1-L141C19 it is possible to use the smtpExistingSecret to specify the name of a secret where the smtp user password is set. Actually this value is never used.
https://github.com/bitnami/charts/blob/main/bitnami/redmine/templates/deployment.yaml#L158 the deployment looks for the smtpPassword value and it uses the password stored in the secret "secretName". So at the moment it is not possible to specify the password in clear in the values using smtpPassword and it is not possible to use a different secret.
No response
The text was updated successfully, but these errors were encountered:
migruiz4
No branches or pull requests
Name and Version
bitnami/redmine 32.0.1
What architecture are you using?
amd64
What steps will reproduce the bug?
In the values.yaml https://github.com/bitnami/charts/blob/main/bitnami/redmine/values.yaml#L141C1-L141C19 it is possible to use the smtpExistingSecret to specify the name of a secret where the smtp user password is set. Actually this value is never used.
https://github.com/bitnami/charts/blob/main/bitnami/redmine/templates/deployment.yaml#L158 the deployment looks for the smtpPassword value and it uses the password stored in the secret "secretName".
So at the moment it is not possible to specify the password in clear in the values using smtpPassword and it is not possible to use a different secret.
Are you using any custom parameters or values?
No response
What is the expected behavior?
No response
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: