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
I'm trying to use helm-unittest 0.2.6 on Windows to test my charts, but I noticed something weird:
Everything works fine with the first 2 test cases
But when I add a 3rd case (identical to the 2nd case, in the same test suite or a separate one), then import-values is not honored and I get nil errors on some global values.
for the first 2 test cases , r.ImportValues is of type <map[string]interface {}>
for the 3rd test case, r.ImportValues is of type <map[string]string>, so it doesn't match any of the switch cases, and values are not imported !
I'm a newbie at Golang and not sure what the root cause may be...
But it's strange that chart object instances would be constructed differently, given it's the same Chart.yaml and test case config.
The text was updated successfully, but these errors were encountered:
I'm trying to use helm-unittest 0.2.6 on Windows to test my charts, but I noticed something weird:
My Chart.yaml has:
The difference I see in the vscode debugger is at:
https://github.com/helm/helm/blob/b1e24764325135b364a7f81fb0aab683d190c546/pkg/chartutil/dependencies.go#L234
for the first 2 test cases , r.ImportValues is of type
<map[string]interface {}>
for the 3rd test case, r.ImportValues is of type
<map[string]string>
, so it doesn't match any of the switch cases, and values are not imported !I'm a newbie at Golang and not sure what the root cause may be...
But it's strange that chart object instances would be constructed differently, given it's the same Chart.yaml and test case config.
The text was updated successfully, but these errors were encountered: