Alan Clucas

I'll have a look at this. We should work out how to support it. GIT_USERNAME and GIT_PASSWORD wouldn't get through Argo CD 2.4's allowed plugin names: https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/2.3-2.4.md#update-plugins-to-use-newly-prefixed-environment-variables I could make...

Would still like to fix this.

```https://[email protected]/MyOrg/my-repo/k8s/base/namespaces``` is what I was thinking of.

I don't use bases myself, no. I use applicationsets with LOVELY_KUSTOMIZE_MERGE/PATCH or sometimes just applications with same for variations. But the differences are minor between instances. I'd like what you're...

The problem with using ArgoCD secrets that it has for access to private repos is that lovely doesn't implement projects, and access to those secrets is guarded by project membership....

**Vault Interop** Regarding ArgoCD Vault Plugin: This was one of the reasons for writing vault-replacer. Deploying a helm chart with values.yaml containing a replacable thing doesn't work in ArgoCD vault...

Thanks for the clear issue description. I'm sure we can support your use case, but as you've concluded, can't do so right now. I'd like to think about the best...

Would still like to fix this

Option 1: provide chartName file in the directory with the chart to override the rendered name. Not great for application reuse perhaps though. Option 2: postpend the directoryname automatically when...

I have the same issue of it saying the resource is namespaced. **However** I am successfully querying that metric from an HPA in a different namespace. ``` metrics: - type:...