intetinte

This is basically what is reported here: https://github.com/helm/helm/issues/12511 Cherrypick this and it will fly https://github.com/helm/helm/pull/12590

I just did some investigation what went wrong in the helm application. All that is in the https://github.com/helm/helm/issues/12511 Zooming out a bit - it is basically "Imported values doesn't override...

My impression is that umbrella chart values takes precedence of child chart values. That implies the umbrella chart could potentially clear values in the child charts.

The current ordering is: 1. User specified values (e.g CLI --set, -f) 2. Parent chart default values 3. Parent chart’s values get propagated to sub-chart(s), and merged with sub-chart values...

I need a way to set values in the sub-charts from the parent chart. Prior to 3.8.2 and in 3.13.0 it is possible to import values in the parent and...

Here an import is done with three helm versions. With three different outcome: Charts: -------------------------------------- $ cat mychart/values.yaml favorite: drink: coffee food: pizza pizzaToppings: - mushrooms - cheese - peppers...

Not sure how to upload the complete package. Anyway there is no difference if I add type: library in the myimport Chart.yaml Basically the target is to create a parent...

I created this: https://gist.github.com/intetinte/93b57e71e1173c0bcc262363b7020f57

I was looking into this test: func TestProcessDependencyImportValuesMultiLevelPrecedence(t *testing.T) { c := loadChart(t, "testdata/three-level-dependent-chart/umbrella") e := make(map[string]string) // The order of precedence should be: // 1. User specified values (e.g...

I actually fixed the problem and did a test verifying it. [helm_changes.patch](https://github.com/helm/helm/files/13427114/helm_changes.patch) [helm_testdata.patch](https://github.com/helm/helm/files/13427117/helm_testdata.patch) Please check and see if this is something that could be used.