Releases: gruntwork-io/terragrunt
Releases · gruntwork-io/terragrunt
v0.1.5
- Terragrunt now compares all settings of the remote configuration between what’s stored in the
.tfstate
file and in .terragrunt
. If any of those settings don’t match up, it prompts the user whether it should re-run terraform remote config
.
- Terragrunt has a new
--terragrunt-non-interactive
flag that can be used to disable user prompts. This is useful when running Terragrunt in an automated setting, such as a scripts or automated test.
v0.1.4
- The
refresh
command now also locks, as it may change the Terraform state file.
v0.1.3
- The
import
and remote push
commands now both properly attain a lock before running.
v0.1.2
terragrunt
now supports specifying a custom path to the .terragrunt
config file using the --terragrunt-config
option or the TERRAGRUNT_CONFIG
environment variable.
v0.1.1
- Update versions of all Go dependencies. We are hopeful this may fix #36.
v0.1.0
BREAKING CHANGE
The syntax for the .terragrunt
file has been modified to use snake_case (which is idiomatic for the HCL language) and to be more consistent between locks and remote state. Please see the root README for the new syntax.
v0.0.11
- Terragrunt now uses
sts.GetCallerIdentity
to fetch a user id instead of iam.GetUser
. This allows it to work with dynamic credentials from STS (from GetSessionToken
) and the AWS_SESSION_TOKEN
environment variable.
v0.0.10
- Build terragrunt using module-ci
v0.0.9
- Terragrunt now detects
CTRL+C
(SIGINT) and will shutdown gracefully and release locks
v0.0.8
- Fix a panic that would occur when using Terragrunt on a totally new repo with no Terraform state files