Is your feature request related to a problem? Please describe.

I want to override helm chart values by providing an arbitrary set of helm values files during zarf package deploy.

Describe the solution you'd like

• Given a Zarf package with a Helm Chart
• When a package deployer provides values files
• Then Zarf overlays those values files onto the identified package:chart at deploy time

Zarf variables are an attractive option when there are only a handful of settings, but applications with dozens or hundreds of key:value pairs cannot be reasonably managed by exposing every setting. Further, maintaining unique Zarf packages with the myriad helm values files is untenable.

Zarf packages contain an unbounded number of components with an unbounded number of helm charts, and the desire is to allow an unbounded number of values files to be written. The 1:many:many:many relationship from package -> component -> chart -> values file.

Recommend adding a new Viper package deploy key VPkgDeployComponentChart that allows referencing helm values file overlays for named charts. An example zarf config file follows.

package:
  deploy:
    components: 'postgres-database'
      charts:
        - name: zalando-postgres
          files:
            - values/ha.yaml
            - values/env-b.yaml