Cleanup hook fired at the beginning instead of at the end when using nested states about helmfile HOT 2 CLOSED

@teksuo Hey! Thanks a lot for reporting. It's very unfortunately this isn't documented anywhere, but it's the expected behavior as of today.

Helmfile is designed around the idea that each sub-helmfile (i.e. nested state) is independent of the parent helmfile.yaml, and should be able to run directly. If the global cleanup was designed to be called after the nested states, it encourages the opposite. The same applies to environment values- environment values aren't automatically inherited down to the nested states, just to encourage you to make those independently runnable.

I'd guess you won't like it, but the best practice here is to repeat your global hooks config within every nested state. You'd want to make it DRY, so I'd suggest considering extracting the global hooks part from the helmfiles and load it by using {{ readFile }}.

from helmfile.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from helmfile.