If you’re using AWS CloudFormation you might have come across clouds-aws. If not you might want to have a look at it on GitHub.
It makes managing CloudFormation stacks from the shell fairly easy. It keeps a local representation of the stack as a Template (JSON or YAML) and a YAML-file holding the parameter values for the stack.
Until now an update to an existing stack had to be performed in the dark, meaning that there was no possibility to dry-run or predict a stack update before going for it without a safety net other than the built-in rollback capability.
The new feature introduced in 0.3.8 brings now change sets to the game allowing to stage a stack update and inspect the changes in detail before actually executing the change.
To get clouds simply run
pip install clouds-aws. You can then dump an existing stack with
clouds dump <stack name>, then edit the stack and create a new change set with
clouds change create <stack name> <change name> which will print out an overview of the changes.
If you need more detail you can inspect the full detail AWS API returns for the change you can describe the change in either YAML or JSON format:
clouds change describe --yaml <stack name> <change name>.
When everything is to your liking you execute the change with
clouds change execute --events <stack name> <change name>. The –events in this example will poll for stack events until the stack reaches a stable state.