Skip to content

Commit efa9046

Browse files
committed
fix: Documentation add ARGOCD_ENV_ prefix to AVP_SECRET variable
Signed-off-by: Ivan Vojtko <ivan.vojtko@gmail.com>
1 parent 810f1fe commit efa9046

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ data:
125125
- name: aws-avp
126126
generate:
127127
command: ["sh", "-c"]
128-
args: ["argocd-vault-plugin generate -s ${AVP_SECRET} ./"]
128+
args: ["argocd-vault-plugin generate -s ${ARGOCD_ENV_AVP_SECRET} ./"]
129129
```
130130

131131
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:
238238
value: foo-team-namespace
239239
```
240240

241-
**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.
241+
**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.

0 commit comments

Comments
 (0)