You know when you have 20 apps and they all are basically configured the same way, but not 100% the same? This is for that problem.
Configamajig will allow you to slurp in a bunch of yaml/json configs, then mix and match them and finally apply them to any type of file.
Real life use case: Helm uses value.yaml files, but you have to deploy your app to multiple environments. Pretty simple, just keep a seperate copy for each env right? Now multiply that by X number of apps. Suddenly the problem becomes much trickier to manage. You can instead keep 1 template file for each app and run configamajig on it. This also makes big changes much easier! All your apps have to switch from one url to another for any number of reasons? Cool, change it once at a global level and every app gets it.
Configamajig will also let you remap files into other properties. Want to dump multiple files under the same reference variable? No problem, just use mappings.
You need to sometimes use one value vs another in an env depending on another defined value? Or maybe you want to switch a bunch of values at once? Great! You can use go templating logic and sprig functions and do that too.
Confused why something doesn't seem to template like you expect? configamajig has full value tracing so you can see which file changed what value super easy!
brew install mtintes/configamajig/configamajig
Or brew tap mtintes/configamajig and then brew install configamajig.
Or find latest build under releases
"configamajig" is a lot for anyone to type out. We recommend setting up an alias!
To generate a basic config file:
configamajig generate config >> config.json
Feed in an template file + a config and out comes a fully filled out file
configamajig replace -c <CONFIG.json> -i <INPUT> -o <OUTPUT>
For finding the value of a specific key
configamajig read key -c <CONFIG.json> -o <OUTPUT>", "some.key"
Wow, um that is super cool if you do want to help. I guess to start read through the current issue and if you think you can solve something or want to take a shot then post something on said issue. I guess we will figure it out from there.