Jake Wernette

AVP has no control over the arguments that a custom plugin can take. That is determined by Argo CD itself https://argo-cd.readthedocs.io/en/stable/operator-manual/config-management-plugins/#using-environment-variables-in-your-plugin. So AVP could only accept env and/or parameters attributes....

Will use this issue to track any work for supporting parameters

You can’t use built in helm with a cmp. Remove this ``` helm: valueFiles: - values.yaml ```

https://argocd-vault-plugin.readthedocs.io/en/stable/usage/#with-helm You can still use a values file, just have to specify it as an env and use that in your template command. ``` source: path: your-app plugin: name: argocd-vault-plugin-helm...

Last I checked no https://github.com/argoproj/argo-cd/issues/11814 but you might want to check with Argo CD to see if that has changed

Helm runs before the value gets injected so .value.oath.username is going to be the path, not a value. That’s why it errors out.

@ilya251188 was the Argo CD issue linked above able to help your issue?

As linked above this is an issue with ArgoCD. https://github.com/argoproj/argo-cd/issues/12476 We have no control over how ArgoCD works AVP is just a custom plugin.

@NitishGupta9282 You can see the Argo CD docs here https://argo-cd.readthedocs.io/en/stable/operator-manual/config-management-plugins/#using-environment-variables-in-your-plugin `The system environment variables (of the repo-server container for argocd-cm plugins or of the sidecar for sidecar plugins)`. If using...

`per-RPC creds failed due to error: compute: Received 403Unable to generate access token; IAM returned 403 Forbidden: Permission 'iam.serviceAccounts.getAccessToken' denied on resource (or it may not exist). This error could...