Releases: LeadingEDJE/stackmanager
Releases · LeadingEDJE/stackmanager
1.2.0
- Enable Termination Protection by default when creating or updating stacks
- If there are no changes when doing a
deploy
, but Termination Protection is not currently enabled, it will add termination protection (whether supplying--auto-apply
or not) - Add
TerminationProtection: False
to the config file if you don't want Termination Protection - Termination Protection will automatically be disabled when you run the
delete
command if set
- If there are no changes when doing a
- Require confirmation for the
delete
command, either by supplying the-Y/--yes
flag, or the interactive prompt.
1.1.0
- Print stack outputs after executing change set or displaying stack status
- Add
get-output
command to return the value of a single output for use in scripting - Errors now go to stderr
1.0.0
- Breaking change:
--config
option changed to--config-file
(short version is still-c
) - #19 Implement chaining between commands with support for calling
build-lambda -> upload -> deploy
with reduced arguments - Allow
--profile
and--region
to be specified before subcommands - Testing for the CLI module
0.8.1
- Add support for
Variables
in configuration that can be substituted intoParameters
,Tags
andStackName
.
0.8.0
- Add
status
command to check current status of stack - Display output from
build-lambda
command - Significantly improved code coverage (but still work to do)
0.7.3
- Add
reject
command to delete a ChangeSet and clean up the stack if it's in REVIEW_IN_PROGRESS and has no remaining ChangeSets.
0.7.2
Bugfix: Add missing arrow library to package
0.7.1
- Improve formatting of timestamps and the reason in the table of events. Use the
STACKMANAGER_TIMEZONE
environment variable to specify the timezone for timestamps to be shown in instead of the automatically detected local timezone (which may be UTC on a build server).
0.7.0
- Allow ChangeSet to be applied using
--change-set-id
without needing to specify--config
or--environment
. - Check for existing ChangeSets in
deploy
and depending upon--existing-changes
value (defaults toALLOW
) prevent deploy from continuing.
0.6.3
Learning to spell the word "on"