coreos
Provide Round-Trip Editing on Ignition Files
I made a simple program to help me understand and debug ignition files. I think this capability might be a reasonable behavior for Butane.
https://github.com/babeloff/fcos-ignition-coder
Please provide more details about this issue. What steps have you tried so far?
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
You know how butane produces ignition files?
Those files contain 'source' elements which are typically base64 encoded, making them difficult to read by us mortals.
The babeloff/fcos-ignition-coder converts an ignition-file into an ignition-directory which contains all the decoded files.
This makes it feasible to look at them to identify issues, edit them and reassemble the ignition-file.
In particular, 'openshift-install create ignition-configs', generates ignition files that I want to tweak and thus fcos-ignition-coder.
After I wrote the thing (wishing openshift-install wrote butane files) I thought it might be of use to you all.
If you are not interested that is fine, just trying to be a good citizen.