Argo-cd: Allow passing adding a source repo for Helm values

[servo1x]

Summary

Follow up on #2682, having the ability to have a git source for values.

Motivation

We have a git monorepo which currently hosts applications that will reference different versions of the same chart. It's really annoying to have to create a local chart every time we want to update a application to reference a different version.

We also follow the application of applications pattern, and if you are using helm 1st class with chart where there are lot of values (100+ lines), it becomes really painful (our app of apps helm chart does not define each app individually, instead - we pass in an array of helm charts and value paths and loop over that to create argocd applications).

Proposal

...
  source:
    repoURL: https://kubernetes-charts.storage.googleapis.com
    chart: my-chart
    targetRevision: 1.0.0
    helm:
      valuesRepo: [email protected]:example/repo.git
      valuesFiles:
        - values/some/value.yaml

[alexec]

Did the solution in the other issue help with this one?

[servo1x]

It's what we're currently doing but we would like move away from that. Currently we have to create local charts for N versions and it becomes very burdensome. It would be a lot nicer if we could reference the chart from the helm repo and use values in the located in our monorepo.

Currently we have a monorepo with values and local charts which have requirements that ref the actual chart...

|[email protected]
|[email protected]
|[email protected]

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[ivanovaleksandar]

Is there any progress on this issue? It seems like a great way to separate runtime environment specific config from a general chart design config.