Joe Julian

I think this is describing what you're asking and works as expected. Play with this and see if you can get the behavior you're experiencing. [base.tar.gz](https://github.com/helm/helm/files/10396973/base.tar.gz)

I don't see a difference. ``` /tmp/foo/chart/wanted $ helm template . --set global.organisationUnit=foo --- # Source: app/charts/appserver/templates/deployment.yaml baseValues: | global: organisationUnit: foo helpers: global: organisationUnit: foo labels: mylabel: "foo" ```...

Ah, I think I see now what you're saying. If I'm now understanding correctly you're saying that these value files: ***base*** ``` globals: base: foo ``` ***subchart1*** ``` globals: subchart1:...

So with the attached charts, each chart defines one global. All globals are printed in each template using: ``` global: {{ nindent 2 (toYaml .Values.global) }} ``` resulting in ```...

closing this as answered.

Assuming that .Values.wildlife is a list of strings, you could: ``` animals = {{ toJson .Values.wildlife }} ```

Well I did say, "Assuming that .Values.wildlife is a list of strings" :) If you want to use a string and split it at some arbitrary character: ``` animals =...

Why am I just learning about helm-playground now? :grin: `values.yaml` ``` wildlife: "lion,cat,tiger" ``` template: ``` config.toml: animals = {{ toJson (splitList "," .Values.wildlife) }} ``` output ``` config.toml: animals...

I'm going to go ahead and close this as answered.

You're successfully demonstrating that the same calls are being placed in the same order until the server returns a 403. I don't see how this could be on the helm...