Changelog for stackctl-1.7.3.0
Unreleased
v1.7.2.0
- Automatically cancel any ongoing update-stack operations on
^C
v1.7.1.0
- Add
withAssumedRole, deprecateassumeRole
v1.7.0.0
-
Retain numeric parameter types, and add boolean parameter handling, in our own yaml generation
This required changing the
Generateto useParametersYamlinstead of[Parameter], and ultimately led us to removing it, hence the major version bump.
v1.6.1.2
- Require Blammo-1.2.2.3
v1.6.1.1
- Fix: finding removed stacks now respects
STACKCTL_DIRECTORY
v1.6.1.0
- Add
Ordinstance onRequiredVersionandRequiredVersionOp
v1.6.0.0
- Re-implement
Stackctl.AWSwithamazonka-mtl.
No CLI or behavior changes.
v1.5.0.1
- Handle missing-or-empty specs directory more explicitly
- Add warning for
Dependspointing to non-existent spec - Fix formatting of required version in warning message
v1.5.0.0
Breaking changes:
- Don't require a name argument to the
awsSimplefunction
New features:
- Add
ExecandShellfeatures inactions[].run - Support lists in
actions[].run(single items still work) - Add more granular status indicators in
stack-ls(1)output, print a legend of these indicators as a footer (disable with--no-legend)
Fixes:
- Fix for redundant change-set creation errors in logging output
- Fix globbing bug in auto-expansion of
--filterarguments
v1.4.4.0
- Add
awsSilently
v1.4.3.0
- Add
awsWithAuth - Add
forEachSpec_
v1.4.2.2
- Use
amazonka-2.0🎉 - Finalize update to
UnliftIO.Exception.Lens - Re-export upstreamed
Blammo.Logging.Colors
v1.4.2.1
No changes. Bumped to trigger release workflow.
v1.4.2.0
- Add
stackctl-lsfor listing stacks and their deployed status - Add
--auto-ssooption for automatingaws sso loginwhen required
v1.4.0.1
- Document and read a consistently-named
STACKCTL_FILTERfor--filter. For now, the old and incorrectSTACKCTL_FILTERSwill still work.
v1.4.0.0
- Add
awsAssumeRolefor running an action as an assumed role - Refactor
Generateinterface to better support generating stacks with pre-existing templates
v1.3.0.2
- Adjust timeout when invoking Lambdas to allow up to Lambda's own execution timeout (15 minutes).
v1.3.0.1
- Fix bug where
LOG_COLORwas never respected - Also accept
"required_version: == <version>" - Add
Eq,ToJSONinstance onRequiredVersion
v1.3.0.0
-
Fix it so commands like
versiondon't need a valid AWS environmentThis changes the
Subcommandinterface and so is a major version update for the purposes of those using Stackctl as a library.
v1.2.0.0
- Use more specific types in
Has{Directory,Filter,Color}Option - Add environment variable configuration for
STACKCTL_{DIRECTORY,FILTERS}
v1.1.4.0
- Support matching Stacks by glob in
capture - Add
--tagtochangesanddeploy
v1.1.3.1
- Fix JSON formatting bugs in generating specification
v1.1.3.0
-
Repository-local configuration
See https://github.com/freckle/stackctl/commit/564678203fe70b5c4c46c655dd3daeaafb6de9e0
-
Don't duplicate re-used templates in
stackctl-cat -
Improve
--filter- Match against stack name and template, in addition to spec path.
- Automatically prepend
**/(unless there is already a leading wildcard) and append{/*,.yaml,.json}(unless there is already a trailing wildcard or extension).
In general, this aims to make
--filtermatch more things more intuitively for operators, but still match exactly in programmatic use-cases. -
Various documentation improvements
-
Support more natural
{Key}: {Value}syntax inParametersandTags -
Fix bug where we may generate an
{}element inParameters
v1.1.2.2
- Add support for Stack descriptions
v1.1.2.1
- Build with LTS-20.4 / GHC 9.2
v1.1.2.0
- Fix incorrect ordering of log-messages by setting
LOG_CONCURRENCY=1 - Fix potential coloring of changes being redirected to a file
- Make
PATHoptional (again) instackctl changes - Add
--no-fliptostackctl capture
v1.1.1.1
- Trigger release
v1.1.1.0
- Add
--parametertochangesanddeploy - Sort changes by causing-before-caused
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
awsLambdaInvokewhen 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
stdoutby default (LOG_DESTINATIONcan still be used) - The
changessubcommand now requires aPATHargument
v1.0.2.0
-
Add
Stackctl.ActionSupport 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.nameorname.id - Read
ParametersasParameter{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