helmDefaults not interpreted when defined in separate file

[msutter]

I use helmfile.d for my releases and a helm-default.yaml file to define global values.
After upgrading to v 0.54.2, the defaults are no longer interpreted in the releases definitions.

I have to workaround this with a dirty inclusion of the helm default file in my release definitions like this:

{{ readFile "000-helm-defaults.yaml" }}
---
releases:
- name: myrelease1
....

The helmDefaults in separated file was working with version 0.45.3

[mumoshu]

@msutter Hey! Thanks for reporting.

I think you've found an interesting use of helmfile.d.
Honestly saying, I have no idea how helm-default.yaml's helmDefaults settings have been propagated/replicated to another helmfiles under the same helmfile.d, without explicitly referring to it(if that's what you meant).

I'll try to see what was going on, but in a certain case you need to wait until the addition of bases which has proposed in #388 (comment).

Out of curiosity, would bases help your use-case, too?

[sonjasutter]

Hi @mumoshu,

Yes sure, bases(includes) would definitively help us to define global vars

[mumoshu]

After #587, you can use bases: ["000-helm-defaults.yaml"] as well. Also, the original workaround of using readFile remains possible.

[mumoshu]

bases will be enabled since helmfile v0.60.0