Select different values file during deployment

[pam2014]

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

Zarf.yaml requires values file to be pre-defined. I have a use case where i need to use the same images with different configuration files in different environments. I do not want to create separate packages for each enviornment

Describe the solution you'd like

Considering zarf uses helm SDK which provides capability to override values file, can this be made available during zarf package deploy?

Describe alternatives you've considered

Alternate option is to create separate zarf yaml per enviornment and separate packages which i do not want to do as it introduces overheads for product managers

Additional context

Add any other context or screenshots about the feature request here.

[Racer159]

@pam2014 have you looked into using https://docs.zarf.dev/examples/variables/? You have to define the interfaces but can provide options on deploy (settable with config files, --set or interactive prompts).

We have been looking at improving some of the flow between variables and Helm (#2131) but decided earlier in the project to not expose the raw Helm values to reduce the variable surface and thus the chance for user error when packages go into an air gapped environment.