You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
When working with large bundles with many helm overrides across many packages the uds-bundle.yaml quickly becomes unwieldy and large from so much extra yaml being under the values in helm overrides. Adopting a pattern similar to how helm already works with values files I think would be beneficial.
Describe the solution you'd like
Given a bundle with many values based helmOverrides
When a values file is provided and referenced in the uds-bundle.yaml
Then those values are passed to the helm chart in that package
Appreciate the issue! This is actually something we've been planning on doing for a while but keep getting distracted. We'll make sure it gets in our backlog
I would also be super interested in a feature like this. Especially with the namespace override, I am now using a single zarf package multiple times. Having the ability to do this would allow me to not repeat overrides within my uds bundle.
Is your feature request related to a problem? Please describe
When working with large bundles with many helm overrides across many packages the uds-bundle.yaml quickly becomes unwieldy and large from so much extra yaml being under the
values
in helm overrides. Adopting a pattern similar to how helm already works with values files I think would be beneficial.Describe the solution you'd like
uds-bundle.yaml
Additional context
possible syntax:
The text was updated successfully, but these errors were encountered: