Skip to content
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

Why duplicate login credentials in values? #250

Open
xeruf opened this issue Feb 19, 2024 · 8 comments
Open

Why duplicate login credentials in values? #250

xeruf opened this issue Feb 19, 2024 · 8 comments

Comments

@xeruf
Copy link

xeruf commented Feb 19, 2024

In the values.yaml you have zammadConfig.postgresql.pass and postgresql.auth.password, stating explicitly that they need to be the same - why not just default one to the other so filling in one is sufficient? Same for redis, but interestingly not for minio it seems.

@monotek
Copy link
Member

monotek commented Feb 19, 2024

Because on of these values confiures the zammad chart and the other the postgres sub chart.

In the end these are just the default values so that the zammad chart can be easily deployed.

In production, where your config likely resides in a git repo, secrets should never be a part of it.
Thats the reason you can define exisiting secrets.

@xeruf
Copy link
Author

xeruf commented Feb 29, 2024

yeah mine are also deployed via gitops, still it adds opportunity to screw up in the config - and I know many other charts where you only need to add the password once so there is apparently some way to access the values of the subchart

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 30, 2024
@xeruf
Copy link
Author

xeruf commented Apr 30, 2024

.

@github-actions github-actions bot removed the stale label May 1, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jun 30, 2024
@mgruner mgruner removed the stale label Jul 1, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Aug 31, 2024
@mgruner mgruner removed the stale label Sep 2, 2024
Copy link

github-actions bot commented Nov 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 1, 2024
@xeruf
Copy link
Author

xeruf commented Nov 5, 2024

this should be a fairly quick fix but I don't have the proper experience here

@github-actions github-actions bot removed the stale label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants