Changelog for stackctl-1.1.0.5
Unreleased
v1.1.0.5
- Trigger release workflow
v1.1.0.4
- Fix bug where only the last spec in a multi-spec case had its changes present
in the output file generated by
changes
.
v1.1.0.3
- Require Blammo-1.1.1.0
v1.1.0.2
- Log responses from
awsLambdaInvoke
when running actions - Clarify discovery logging
- Add install script
v1.1.0.1
- Update to
cfn-flip-0.1.0.3
v1.1.0.0
- Fix interleaved or out-of-order output bugs by streaming deployment events
through the Logger instead of directly to
stdout
- Logging goes to
stdout
by default (LOG_DESTINATION
can still be used) - The
changes
subcommand now requires aPATH
argument
v1.0.2.0
-
Add
Stackctl.Action
Support for taking actions during Stack management, currently we support invoking a lambda post-deployment. In the future, we can add more, such as running local pre-deploy validation or preparation scripts.
-
Add
awsCloudFormationDescribeStackOutputs
v1.0.1.2
- Always flush log messages before our own output
v1.0.1.1
- Respect
LOG_DESTINATION
(the default remainsstderr
)
v1.0.1.0
-
Support reading CloudGenesis specifications
- Accept account paths like
id.name
orname.id
- Read
Parameters
asParameter{Key,Value}
or{Name,Value}
This allows us to work with specifications directories originally implemented for, and potentially still used with, the CloudGenesis tooling.
- Accept account paths like
v1.0.0.2
- Fix tailing all events to read most recent, causing Throttling errors
v1.0.0.1
- Fix non-portable paths issue in OSX executable build
v1.0.0.0
First release