realestate-com-au / stackup

a simple CLI and Ruby API for AWS CloudFormation
MIT License
97 stars 34 forks source link

Multiple params files. #29

Closed tigris closed 8 years ago

tigris commented 8 years ago

Currently if you want to maintain a deployment parameter, such as Version or something, in a params file, your only option is to include this in the same params.json file as all your other (probably environment) params.

This makes automating the update of that param harder, since there might be 20+ params in there, you are using a tool like jq or something to manipulate the file, hoping you don't accidentally change any other params.

It would be handy if stackup up could take multiple -p arguments. That way, the Version param you are maintaining can be in a file all of it's own, and you don't necessarily need to use a tool like jq to edit it. A simple echo '{"Version": "..."}' > version.json will suffice, no external json parsing tools required.

Obviously with this change comes the issue of which params file should the real param come from. As an end-user I would assume the last one. E.g. up -p params.json -p version.json ..., then if params.json also had a Version in it, it would get overridden. Much like a -o Version=... will also override both of them.