Environment specific helm values.yaml without Zarf-Variables

[unknown0816]

Hi, Is it possible to provide a environment specific values.yaml during the zarf package deploy command? I currently have lots of config values inside the values.yaml and I don't want to recreate all of them with a Zarf variable.. This seams wrong to me, because I must maintain both sides all the time.
Did I miss something or is there a specific parameter that I couldn't find to provide a extra values.yaml during the deploy command?

[brandtkeller]

Hey @unknown0816 !

We very much agree with you - Zarf Variables are not as extensible or dynamic.

We have an alpha feature that should be moving to beta and enabled by default soon to which we call package values.

This allows you to specify a values.yaml file (or named as you wish) that you can both bake into the package (sane defaults) and override values at deploy-time.

Keep in mind a zarf package may have many charts,manifests,files,actions that we allow templating - so this isn't a feature to say "pass this values file to this specific helm chart on deploy" specifically but instead you can map how helm charts receive specific values and organize them accordingly from the top level values file.

Thereafter you can also include a schema in the package which will allow input validation.