BREAKING CHANGES
Important
When using nested stacks and tags in before
and after
the order of execution was wrong.
This is now fixed but but can lead to a change in the order of execution in some rare cases.
Please check the terramate list --run-order
after upgrading to ensure you run stacks in the correct order.
Added
- Add
terramate.config.generate.hcl_magic_header_comment_style
option to change the comment style for magic headers to#
instead of//
- Add support for formatting single files or stdin with
terramate fmt
- Add support for
--cloud-status
filter toterramate run
- Add support for
--cloud-status
filter toterramate script run
- Add support to synchronize previews to Terramate Cloud via new
terramate run --cloud-sync-preview
- Add
script.name
attribute.- The commands
terramate script info
,terramate script list
andterramate script tree
were updated to show the script name (when available).
- The commands
- Improve user experience when using Terramate with existing Terragrunt projects.
- Add
terramate create --all-terragrunt
option, which will automatically create Terramate stacks for each Terraform module.
- Add
- Allow to run independent stacks in parallel for faster deployments and better utilization of system resources in general.
- Add
--parallel
(short-j
) option toterramate run
andterramate script run
. --parallel=N
limits the number of concurrent runs toN
, otherwise a sensible default limit is chosen.- Ordering constraints between stacks are still respected, i.e.
before
/after
, parent before sub-folders.
- Add
Fixed
- Fix a panic in language server with a project caontaining errors on root directory
- Fix the execution order when using
tag
filter inafter/before
in conjunction with implicit order for nested stacks. (BREAKING CHANGE)