helmfile/test/integration/test-cases/issue-2451-nested-helmfile-array-replace/input/helmfile.yaml at 4e3677dedbf536fa9b82e720596ac66a8bdda276 - helmfile - Gitea: Git with a cup of tea

public_git/helmfile

mirror of https://github.com/helmfile/helmfile.git synced 2026-10-01 12:33:02 +02:00

Files

T

Aditya Menon c375b48550 fix: nested helmfile values should replace arrays, not merge element-by-element (#2458 )

PR #2367 introduced CLIOverrides to give --state-values-set element-by-element
array merge semantics. However, nested helmfile values (helmfiles[].values:)
were also routed into CLIOverrides, causing their arrays to merge instead of
replace. This broke the pre-v1.3.0 behavior where passing an array via
helmfiles[].values: would fully replace the child's default array.

Add OverrideValuesAreCLI flag to SubhelmfileEnvironmentSpec so the loader can
distinguish CLI flags from nested helmfile values. CLI values continue using
CLIOverrides (element-by-element merge); nested helmfile values now use Values
(Sparse merge strategy → full array replacement).

Fixes #2451

Signed-off-by: Aditya Menon <amenon@canarytechnologies.com>

2026-03-09 18:31:21 +08:00

6 lines

93 B

YAML

Raw Blame History

 helmfiles:
   - path: child.yaml.gotmpl
     values:
       - list:
           - name: override1