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
Right now some secrets can only be set via the config file, for example:
auth.sessionStore.secret
auth.oidc.clientSecret
auth.gitlab.clientSecret
It would be great if those could be passed via an environment variable or optionally mounted as secret file.
Right now I need to treat the whole config.yaml as a secret itself, which is a bit cumbersome.
Edit: I just noticed that the official helm chart already has a solution for injecting secrets into the config.yaml, which seems to work but is just not documented: https://github.com/freifunkMUC/wg-access-server-chart/blob/4061059fff247c632c3e557963f5b0d39d6903ee/charts/wg-access-server/templates/deployment.yaml#L32
The text was updated successfully, but these errors were encountered:
@andi0b Would you be open to adding that to the documentation?
Sorry, something went wrong.
No branches or pull requests
Right now some secrets can only be set via the config file, for example:
auth.sessionStore.secret
auth.oidc.clientSecret
auth.gitlab.clientSecret
It would be great if those could be passed via an environment variable or optionally mounted as secret file.
Right now I need to treat the whole config.yaml as a secret itself, which is a bit cumbersome.
Edit: I just noticed that the official helm chart already has a solution for injecting secrets into the config.yaml, which seems to work but is just not documented: https://github.com/freifunkMUC/wg-access-server-chart/blob/4061059fff247c632c3e557963f5b0d39d6903ee/charts/wg-access-server/templates/deployment.yaml#L32
The text was updated successfully, but these errors were encountered: