From d8bd730ea15025d8a993ad019cf4cfef3356f61a Mon Sep 17 00:00:00 2001 From: Ivan Vojtko Date: Wed, 3 Jul 2024 15:41:56 +0200 Subject: [PATCH] fix: Documentation add ARGOCD_ENV_ prefix to AVP_SECRET variable --- docs/config.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/config.md b/docs/config.md index 64b64494..c592efc1 100644 --- a/docs/config.md +++ b/docs/config.md @@ -125,7 +125,7 @@ data: - name: aws-avp generate: command: ["sh", "-c"] - args: ["argocd-vault-plugin generate -s ${AVP_SECRET} ./"] + args: ["argocd-vault-plugin generate -s ${ARGOCD_ENV_AVP_SECRET} ./"] ``` Notice that the secret name is parametrized via an environment variable. This means each Argo app manifest can set `AVP_SECRET` to be the name of the Kubernetes secret that contains the configuration for the backend needed to generate its secrets. @@ -238,4 +238,4 @@ spec: value: foo-team-namespace ``` -**Note**: Exposing tokens (like `AVP_ROLE_ID` or `AVP_SECRET_ID`) in plain-text in Argo CD app manifests should be avoided. Prefer to pass those tokens through one of the means mentioned above. \ No newline at end of file +**Note**: Exposing tokens (like `AVP_ROLE_ID` or `AVP_SECRET_ID`) in plain-text in Argo CD app manifests should be avoided. Prefer to pass those tokens through one of the means mentioned above.