Releases: terramate-io/terramate
Releases · terramate-io/terramate
v0.11.1
v0.11.1-rc1
Added
- Faster code generation through parallelization.
- Enabled by default, use
terramate generate --parallel <n>
to control the amount of concurrent units (default = number of logical CPU cores).
- Enabled by default, use
v0.11.0
Added
- Add
--enable-change-detection=<options>
and--disable-change-detection=<options>
to the commands:terramate list
,terramate run
andterramate script run
.- These flags overrides both the default change detection strategy and the configuration in
terramate.config.change_detection.git
block.
- These flags overrides both the default change detection strategy and the configuration in
- Add support for using
TM_ARG_*
environment variables to configure cli commands.
Note: This is an incremental change. Only global flags andterramate run
flags were added for now.- For example: Use
TM_ARG_CHDIR=stacks/prod TM_ARG_RUN_REVERSE=1 terramate run -- terraform apply
to run from insidestacks/prod
and with reversed execution order (which is the same asterramate --chdir stacks/prod run --reverse -- terraform apply
).
- For example: Use
Changed
- (Breaking change) The
terramate list --changed
now considers untracked and * uncommitted* files for detecting changed stacks.- This behavior can be turned off by
terramate.config.change_detection.git.untracked = "off"
andterramate.config.change_detection.git.uncommitted = "off"
.
- This behavior can be turned off by
- (Breaking change) Remove the deprecated
terramate experimental run-order
.- The
terramate list --run-order
was introduced in versionv0.4.5
and provides the same functionality as the removed command.
- The
v0.11.0-rc2
Added
- Add
--enable-change-detection=<options>
and--disable-change-detection=<options>
to the commands:terramate list
,terramate run
andterramate script run
.- These flags overrides both the default change detection strategy and the configuration in
terramate.config.change_detection.git
block.
- These flags overrides both the default change detection strategy and the configuration in
- Add support for using
TM_ARG_*
environment variables to configure cli commands.
Note: This is an incremental change. Only global flags andterramate run
flags were added for now.- For example: Use
TM_ARG_CHDIR=stacks/prod TM_ARG_RUN_REVERSE=1 terramate run -- terraform apply
to run from insidestacks/prod
and with reversed execution order (which is the same asterramate --chdir stacks/prod run --reverse -- terraform apply
).
- For example: Use
Changed
- (Breaking change) The
terramate list --changed
now considers untracked and * uncommitted* files for detecting changed stacks.- This behavior can be turned off by
terramate.config.change_detection.git.untracked = "off"
andterramate.config.change_detection.git.uncommitted = "off"
.
- This behavior can be turned off by
- (Breaking change) Remove the deprecated
terramate experimental run-order
.- The
terramate list --run-order
was introduced in versionv0.4.5
and provides the same functionality as the removed command.
- The
v0.10.9
Added
- Add support for dot (
.
) in the tag syntax.- Now you can add tags like
v1.0.0-abc_xyz
- Now you can add tags like
Changed
- The Outputs Sharing feature now has no default value for the
sensitive
field ofinput
andoutput
blocks.
v0.10.9-rc1
Added
- Add support for dot (
.
) in the tag syntax.- Now you can add tags like
v1.0.0-abc_xyz
- Now you can add tags like
Changed
- The Outputs Sharing feature now has no default value for the
sensitive
field ofinput
andoutput
blocks.
v0.10.8
Fixed
- Fix Outputs Sharing feature not generating the
output.sensitive
attribute. - Fix Outputs Sharing feature not generating the
variable.sensitive
attribute.
v0.11.0-rc1
Added
- Add
--enable-change-detection=<options>
and--disable-change-detection=<options>
to the commands:terramate list
,terramate run
andterramate script run
.- These flags overrides both the default change detection strategy and the configuration in
terramate.config.change_detection.git
block.
- These flags overrides both the default change detection strategy and the configuration in
Changed
- (Breaking change) The
terramate list --changed
now considers untracked and * uncommitted* files for detecting changed stacks.- This behavior can be turned off by
terramate.config.change_detection.git.untracked = "off"
andterramate.config.change_detection.git.uncommitted = "off"
.
- This behavior can be turned off by
Fixed
- Fix
trigger --ignore-change
not ignoring stacks changed due to Terraform or Terragrunt changes.
v0.10.7
Added
- Add
terramate create --wants ... --wanted-by ...
flags for configuring thestack.wants
andstack.wanted_by
attributes, respectively.
Fixed
- Fix the cleaning up of orphaned files in the
terramate generate
to respect the-C <dir>
flag. - Fix the value of
terramate.stack.path.basename
andterramate.root.path.basename
which were given the value of"\\"
in the case the stack was defined at the project root directory.
Changed
- Several performance improvements in the change detection.
v0.10.7-rc1
Added
- Add
terramate create --wants ... --wanted-by ...
flags for configuring thestack.wants
andstack.wanted_by
attributes, respectively.
Fixed
- Fix the cleaning up of orphaned files in the
terramate generate
to respect the-C <dir>
flag. - Fix the value of
terramate.stack.path.basename
andterramate.root.path.basename
which were given the value of"\\"
in the case the stack was defined at the project root directory.
Changed
- Several performance improvements in the change detection.