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
It would become a lot easier to reuse the releases with minor changes if the releases could be a collection of maps/dictionaries instead of lists. For example, it would allow the use of yaml anchors or maybe other templating engines (go templates or jsonnet or anything) to reuse the contents of a previous release with minor changes.
I'm not a maintainer, and I'm not that good at golang, but I predict this would be tricky (or impossible?) to parse that yaml into a struct since keys such as myvault can't be dynamically defined as a top-level key. If the repetition is bad enough you might get some lift out of pre-processing the helmfile.yml with a tool like ytt... which I know, that's what everybody loves to hear, "use more yaml templating!", but it could be worth investigating? Will back off, don't mean to hijack your thread & maybe a maintainer has better insights / could offer a better solution, just putting out (unsolicited) feedback 👌
It would become a lot easier to reuse the releases with minor changes if the
releases
could be a collection of maps/dictionaries instead of lists. For example, it would allow the use of yaml anchors or maybe other templating engines (go templates or jsonnet or anything) to reuse the contents of a previous release with minor changes.Current:
Expected:
Not the best example, but should be enough to get the idea.
The text was updated successfully, but these errors were encountered: