v0.10.2

• #128: You can now specify extra_arguments in your Terragrunt configuration which specify custom arguments to pass to Terraform for specific commands. For example, you can specify custom -var-file arguments to pass to Terraform for the apply and plan commands. For more details, check out the docs here.

v0.10.1

• BUG FIX: When downloading remote Terraform configurations into a temp folder, Terragrunt would first delete the existing configs in that tmp folder to ensure you had the latest code. Unfortunately, it also deleted the .tf files in the .terraform folder, so that you would get a "module not found" error. #126

v0.10.0

MAJOR CHANGE: Terragrunt now expects its configuration to be defined in a terraform.tfvars file instead of a .terragrunt file. Check out the README for what the terraform.tfvars file should look like and the migration instructions for how to move to the new format (it's VERY easy!). For backwards compatibility, the .terragrunt format WILL continue to work, but it is now deprecated.

The main reasons for this change are:

1. Instead of introducing a new file format into your Terraform projects, Terragrunt now piggybacks on top of the .tfvars format Terraform already uses for defining variables.
2. We reduce the number of files you need. This is especially valuable with remote Terraform configurations, as it means you only need a single terraform.tfvars file to define what code to download and provide the variables for that code.

v0.9.9

• When Terragrunt downloads source code, it will now download the entire repository (i.e. the part before the double-slash // in the URL). This way, relative paths between modules in that repository should work correctly.

v0.9.8

• Terragrunt now supports a --terragrunt-source-update flag. If set, Terragrunt will delete the contents of the temporary folder to clear out any old, cached source code before downloading new source code into it.

v0.9.7

• When downloading remote Terraform configurations, Terragrunt will now cache the download in a temporary folder, and only re-download the files when necessary. This way, you don't have to download source code, download modules, and configure remote state for every single Terragrunt command.

v0.9.6

• When you run terragrunt foo, Terragrunt will now only send the output of the foo command to stdout. The output from any other commands Terragrunt might run, such as terraform remote config or terraform get will now be redirected to stderr. This allows you to parse the stdout of your Terraform commands without worrying about them being polluted by unrelated logging.

v0.9.5

• Terragrunt now allows you to specify a login profile to use by specifying a profile key in the config block of the DynamoDB lock and the config block of remote state (the latter only applies when using S3).

v0.9.4

• Terragrunt can now download Terraform templates from a specified URL into a temporary folder and run Terraform in that temporary folder. This can dramatically reduce the amount of copy/paste in Terraform projects, allows you to version all of your code, and to promote immutable versions of that code through each of your environments (e.g. qa -> stage -> prod). See the Terraform remote configurations documentation for more info.

v0.9.3

• Terragrunt now displays clear error messages when you try to release a lock on a table or item that does not exist in DynamoDB