Because of what seems like an intended behavior of Helm, resources defined in a dependency chart get double-rendered unless the *.tgz files are removed from the charts/ directory as well as the template files that were extracted from the tarballs.
I0529 23:14:12.259257 625 patch.go:141] generating /run/user/1000/2245639347060509570/helmx.2.patched.yaml
TestIntegration: integration_test.go:75: Integration test failed: exit status 1
OUTPUT:
2020/05/29 23:14:12 got file 'configmap.yaml', but '/run/user/1000/2245639347060509570/helmx.1.rendered/helm-chart/charts/subchart/templates/configmap.yaml' must be a directory to be a root
Error: accumulating resources: merging resources from 'helmx.1.rendered/helm-chart/charts/subchart/templates/configmap.yaml': may not add resource with an already registered id: ~G_v1_ConfigMap|~X|subchart
Applying multiple json patches
The PR makes it so that os.Mkdir is called only for the first json patch. There might be a more elegant way of handling this, but my go-lang knowledge is limited.
Contains two fixes for...
Chartifying with dependencies
Because of what seems like an intended behavior of Helm, resources defined in a dependency chart get double-rendered unless the
*.tgz
files are removed from thecharts/
directory as well as the template files that were extracted from the tarballs.Applying multiple json patches
The PR makes it so that
os.Mkdir
is called only for the first json patch. There might be a more elegant way of handling this, but my go-lang knowledge is limited.