Added
- Add support for
[for ...]
and{for ...}
expressions containing Terramate variables and functions inside thegenerate_hcl.content
block. - Add experimental support for deployment targets. This allows to keep separate stack information when the same stacks are deployed to multiple environments, i.e. production and staging.
- Can be enabled with
terramate.config.experiments = ["targets"]
andterramate.config.cloud.targets.enabled = true
. - Once enabled, commands that synchronize or read stack information to Terramate Cloud require a
--target <target_id>
parameter. These include:terramate run --sync-deployment/--sync-drift-status/--sync-preview
terramate script run
terramate run --status
terramate list --status
terramate cloud drift show
- Can be enabled with
- Add
script.lets
block for declaring variables that are local to the script. - Add
--ignore-change
flag toterramate experimental trigger
, which makes the change detection ignore the given stacks.- It inverts the default trigger behavior.
- Add
--recursive
flag toterramate experimental trigger
for triggering all child stacks of given path.
Fixed
- Fix
terramate experimental trigger --status
to respect the-C <dir>
flag.- Now using
-C <dir>
(or--chdir <dir>
) only triggers stacks inside the provided dir.
- Now using
- Fix the update of stack status to respect the configured parallelism option and only set stack status to be
running
before the command starts. - Fix
terramate experimental trigger
gives a misleading error message when a stack is not found.
Changed
- (BREAKING CHANGE) The format of the generated code may change while being still semantically the same as before. This change is marked as "breaking", because this may trigger change detection on files where the formatting changes.