- Requires the Racket programming language if building from source.
- Standalone executable requires awscli to run commands. Assumes you have already set up your awscli profiles.
Once compiled the standalone executable has no dependencies besides the awscli.
Download the latest executable from repo’s releases and add it somewhere in your path.
Ensure you have racket installed. Run the following commands to build the standalone executable from source.
git clone https://github.com/Nan0Scho1ar/cftool
cd cftool
make
Install the built executable.
sudo make install
Pull the latest changes then run:
make clean
make
sudo make install
Run the following command to uninstall cftool.
sudo make uninstall
Help text can be displayed by running cftool --help
.
cftool -e prod -c my-website
cftool -e prod -u my-website
cftool -e prod -d my-website
cftool -e prod -cg my-group
cftool -e prod -ug my-group
cftool -e prod -dg my-group
Returns a list of stack templates which can be created/updated/deleted using cftool
.
cftool -l
Returns a list of stack groups which can be created/updated/deleted using cftool
.
cftool -lg
If you provide the -D
(short form of --dry-run
) flag to cftool, it will print the awscli
commands which will be called to perform the requested action, instead of running the commands. This can be quite useful when trying to debug an error (e.g incorrect stack params), or check that a new definition in the config results in sensible looking commands, before running it for real on the specified environment/account.
NOTE: There is some parameter quote/escape handling done under the hood for the calls to awscli
.
This means that some of the commands output by -D
will not “just work” if you copy paste them into a terminal.
This is because the -D
flag does not currently print the parameters pre-wrapped in quotes.