You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report
In the recently merged large PR #7804, the vault auth param was moved from a pair of secrets (Values.secrets.vaultAppRoleId,Values.secrets.vaultAppRoleSecretId) into a chart value (concourse.web.vault.authParam) that doesn't have a corresponding entry in secrets.yaml.
But since CONCOURSE_VAULT_AUTH_PARAM is supposed to be used to pass secret credentials, the helm chart should treat them as secret credentials - and allow keeping them out of helm/tiller.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
stalebot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Nov 1, 2018
Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report
In the recently merged large PR #7804, the vault auth param was moved from a pair of secrets (
Values.secrets.vaultAppRoleId
,Values.secrets.vaultAppRoleSecretId
) into a chart value (concourse.web.vault.authParam
) that doesn't have a corresponding entry insecrets.yaml
.But since
CONCOURSE_VAULT_AUTH_PARAM
is supposed to be used to pass secret credentials, the helm chart should treat them as secret credentials - and allow keeping them out of helm/tiller.The text was updated successfully, but these errors were encountered: