Because using cloudformation is just too damn hard...
cftool is a theoretical tool to make it easier to interact with
cloudformation. The idea is that you can declare your stacks in a series of
yaml state files. Then you can use cftool to apply changes.
Filters are currently limited and simply check for the existence of the word in the region, local name, or stack name. So if you send the filters "us-east" and "chat" you will get all stacks that say "chat" and all stacks in "us-east".
cftool status [<filter1>...]
Gets the status of the managed stacks.
AWS REGION STACKNAME INTERNAL NAME CLOUDFORMATION DRIFT TEMPLATE DRIFT
---------------- ----------------------- --------------- ---------------------- ----------------
eu-west-1 dublin-region-chat-c1 dublin:c1 NOT_CHECKED Yes
ap-southeast-2 sydney-region-chat-c1 sydney:c1 NOT_CHECKED No
us-east-1 chat-c1 us_east:c1 NOT_CHECKED No
-
cftool diff [<filter1>...]PARTIALY COMPLETE Upload a copy of the new template and generate a change set of what would change. This currently prepares the changeset but does not upload it, nor prints out what would change. -
cftool fetch [<filter1>...]Sync the parameters, and stacks from AWS to the local disk. -
cftool diff-templateGrabs the live template, and gives a diff against the local version. -
cftool ssh [<filter1>]Grabs an IP from the filtered stack and execs ssh to the box.
-
config.yamlLists the config for your setup. This could include things such as:- account ID
- regions to whitelist
- stacks to ignore
-
individual stacks:
# file: examples/chat/us-east-c1.yml
---
name: "us_east:c1"
region: "us-east-1"
arn: "arn:aws:cloudformation:us-east-1:185583345998:stack/chat-c1/9a2046e0-35da-11e9-900e-0e0ed2de56d2"
file: "../../GetStream/stream-puppet/cloudformation/v2/shard-chat.yml"