Changelog of @hackage/stackctl 1.1.3.0

Unreleased

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 --filter match more things more intuitively for operators, but still match exactly in programmatic use-cases.
Various documentation improvements
Support more natural {Key}: {Value} syntax in Parameters and Tags
Fix bug where we may generate an {} element in Parameters

Fix bug where only the last spec in a multi-spec case had its changes present in the output file generated by changes.

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 a PATH argument

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

Support reading CloudGenesis specifications
- Accept account paths like id.name or name.id
- Read Parameters as Parameter{Key,Value} or {Name,Value}
This allows us to work with specifications directories originally implemented for, and potentially still used with, the CloudGenesis tooling.

First release