-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add ability to capture finalized helmfile releases yaml to disk #752
Comments
Hey! Would you mind clarifying a bit more on:
Can't we use a GitOps repo containing either (1)
What would be the benefit of this over
This is really interesting. What would be the purpose to do so?
In which circumstance would you need to do so? |
My ideal goal is that my team can run helmfile to generate and apply a set of releases, using a single command (without need for them to go write a wrapper or parse output etc), or at most 2 commands (apply/sync + template)
I just want to easily get the The helmfiles I'm working can generate a lot of releases when the team is debugging sometime or in a pinch situation it can often be helpful just be able to look at a clean dump of generated releases without all the extra processing info. I also want to be able to save these as static releases that get generated and be able to use them as a teaching aid for helping others create their own helmfile templates. The generated |
Thanks! So you'll be using generated static bundles of helmfile for auditing and debugging purpose? If so, would it be duplicate of #195, or just similar to it? I'd like to hear your opinion. |
Yeah I don't think #195 is what is really what I'm talking about. Let me try to clarify by referencing this example at: https://github.com/bitsofinfo/helmfile-deploy/tree/master/examples All I am interested in is given a helmfile, that generates many helm Right now to get the generated
I get this output back: (I cut out a large chunk for brevity)
The above is a lot of output that I am not interested in. Out of the above output, all I am interested is what follows below, without the line numbers:
I guess what I want to do exactly with this releases output is not super relevant imho, but in the end, I simply would like to get this That said, I'm well aware I could certainly pipe this output to another routine that parses out what I want, but I'm just curious if such a command line option could be added that could give me this without much trouble. If its a ton of work then just forget it I guess. I'd qualify this as more of a nice to have. |
In line w/ #751 and #629 would be great to be able to capture the finalized helmfile generated
releases
(to stdout or preferably just write the YAML to another output dir)For my use case, the releases are generated and the helmfile is primarily a template. I'd like to be able to capture the finalized/generated helmfile
releases
and flush to YAML for both auditing purposes, offline debugging and more importantly if we want to use the generated helmfiles as future static ones. (or if I just want to re-run it manually without going through the original helmfile that generated it)The text was updated successfully, but these errors were encountered: