The regression test only nulled a top-level key, but the bug (and
pruneNilOverrides) is about pruning explicit nil overrides at
arbitrary depth. Switch it to null services.myservice.image, matching
the nesting in #30765, and also assert the sibling key set alongside
it survives.
Signed-off-by: BeganovR <446110@niuitmo.ru>
req.True(ok,"expected services.myservice key in persisted config")
is.NotContains(myservice,"image","explicit null should remove the nested key from the persisted config, at whatever depth it appears")
is.Equal("1.0.0",myservice["tag"])
is.Contains(res.Manifest,"image: chart-default","nulling a reused nested value should fall back to the chart default on the first upgrade, not the second")