You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Morten Torkildsen 82d01cb312 fix(helm): Merge nested values correctly on upgrade (#4806) ... Upgrading a release and override existing values doesn't work as expected for nested values. Maps should be merged recursively, but currently maps are treated just like values and replaced at the top level. If the existing values are: ```yaml resources: requests: cpu: 400m something: else ``` and an update is done with ```--set=resources.requests.cpu=500m```, it currently ends up as ```yaml resources: requests: cpu: 500m ``` but it should have been ```yaml resources: requests: cpu: 500m something: else ``` This PR updates the way override values are merged into the existing set of values to merge rather than replace maps. Closes: #4792 Signed-off-by: Morten Torkildsen <mortent@google.com>		8 years ago
..
testdata	…
capabilities.go	…
capabilities_test.go	…
chartfile.go	…
chartfile_test.go	…
create.go	Reform indentation practices using nindent (#4562)	8 years ago
create_test.go	Add test template example for helm create (#4524)	8 years ago
doc.go	…
expand.go	…
files.go	…
files_test.go	…
load.go	…
load_test.go	…
requirements.go	…
requirements_test.go	…
save.go	Remove executable bits from chartutil generated files (#4839)	8 years ago
save_test.go	…
transform.go	…
values.go	fix(helm): Merge nested values correctly on upgrade (#4806)	8 years ago
values_test.go	fix(helm): Merge nested values correctly on upgrade (#4806)	8 years ago