Skip to content

Commit

Permalink
docs: Update plugin usage documentation
Browse files Browse the repository at this point in the history
The CMP-managed plugin documentation for using Helm values was still using a
non `ARGOCD_ENV_` prefixed environment variable setup which only works on ArgoCD
version before 2.4. This change adds the prefix in the corresponding code
examples.

Signed-off-by: Duco van Amstel <[email protected]>
  • Loading branch information
Helcaraxan authored and werne2j committed Mar 21, 2023
1 parent 1eb3dfc commit 98e3987
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ configManagementPlugins: |
- name: argocd-vault-plugin-helm
generate:
command: ["bash", "-c"]
args: ['helm template "$ARGOCD_APP_NAME" -f <(echo "$HELM_VALUES") . | argocd-vault-plugin generate -']
args: ['helm template "$ARGOCD_APP_NAME" -f <(echo "$ARGOCD_ENV_helm_values") . | argocd-vault-plugin generate -']
```
For sidecar configured plugins, add this to `cmp-plugin` ConfigMap, and then [add a sidecar to run it](../installation#initcontainer-and-configuration-via-sidecar):
```yaml
Expand All @@ -168,7 +168,7 @@ For sidecar configured plugins, add this to `cmp-plugin` ConfigMap, and then [ad
- bash
- "-c"
- |
helm template $ARGOCD_APP_NAME -n $ARGOCD_APP_NAMESPACE -f <(echo "$ARGOCD_ENV_HELM_VALUES") . |
helm template $ARGOCD_APP_NAME -n $ARGOCD_APP_NAMESPACE -f <(echo "$ARGOCD_ENV_helm_values") . |
argocd-vault-plugin generate -
lockRepo: false
```
Expand All @@ -180,7 +180,7 @@ Then you can define your Helm values inline in your application manifest:
plugin:
name: argocd-vault-plugin-helm
env:
- name: HELM_VALUES
- name: helm_values
value: |
# non-vault helm values are specified normally
someValue: lasldkfjlksa
Expand Down

0 comments on commit 98e3987

Please sign in to comment.