v0.5.0

• Terragrunt now stores the user ARN, rather than the user ID, in DynamoDB. The ARN typically includes a human-readable username, which will make it easier to tell who actually has a lock.

v0.4.0

• ENHANCEMENT: Terragrunt now supports an include block and several helpers that you can use in the .terragrunt file to reuse settings from another .terragrunt file. This significantly reduces the amount of copy/paste and manual maintenance you have to do if you are maintaining multiple Terraform folders (and thereby, multiple .terragrunt files). For usage instructions, see: https://github.com/gruntwork-io/terragrunt/tree/inherit#managing-multiple-terragrunt-files

v0.3.0

• Terragrunt now supports an acquire-lock command that can be used to create long-term locks.

v0.2.0

• ENHANCEMENT: If you configure s3 as your remote state store, Terraform will now create the S3 bucket for you (prompting you for confirmation first) if that bucket doesn't already exist. It'll also warn you if the bucket doesn't have versioning enabled or if your remote state config doesn't have encryption enabled.
• BUG FIX: Terragrunt will now properly read in --terragrunt-XXX flags, even if they are specified after the command (e.g. terragrunt apply --terragrunt-non-interactive). This was broken before due to a limitation in the CLI library we were using.
• BUG FIX: The integration test for Terragrunt now creates the S3 bucket for itself rather than using a hard-coded one that only Gruntwork employees can access.

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.