v0.13.13

#325: The xxx-all commands can now use the --terragrunt-source parameter. See Testing multiple modules locally for details.

v0.13.12

#324: You can now use the validate-all command to validate all modules in a folder.

v0.13.11

#323: You can now tell Terragrunt to assume an IAM role using the --terragrunt-iam-role argument or TERRAGRUNT_IAM_ROLE environment variable. This offers a convenient way to use Terragrunt/Terraform with multiple AWS accounts. See Work with multiple AWS accounts for more details.

v0.13.10

#322: If you specify the role_arn parameter in your S3 backend config, Terragrunt will now automatically assume that IAM role before configuring remote state, creating the S3 bucket, creating the DynamoDB table, etc. This is very useful for multi-account setups where you may need to assume an IAM role in another account.

v0.13.9

#321: The find_in_parent_folders helper now takes a second optional param that is a fallback value.

v0.13.8

#320: The find_in_parent_folders helper now accepts an (optional) parameter that tells it the filename to look for.

v0.13.7

#309: Terragrunt now properly handles the dynamodb_table param, auto-creating the DynamoDB table as necessary.

v0.13.6

#308: Terragrunt should now do a better job of checking if S3 backends need initialization, including creating the DynamoDB table automatically, even if the S3 bucket already exists.

v0.13.5

#302: Terragrunt will now exit with an error if you define remote_state settings in terraform.tfvars, but your Terraform code does not define a corresponding backend.

v0.13.4

#301: Terragrunt should now do a better job of checking whether there is source code downloaded into your tmp folder and hopefully avoid the "No Terraform configuration files found in directory" error message.