v0.6.4

• Fixes #81, where terragrunt spin-up would only search in immediate subfolders, but not recursive subfolders.

v0.6.3

• Fix a bug where the spin-up and tear-down commands did not properly call terraform get for modules that depended on other modules.

v0.6.2

• Fix a bug in the find_in_parent_folders helper where it would not handle relative paths correctly.
• Fix documentation in the Terragrunt --help command.

v0.6.1

• Fix typo in Terragrunt log output

v0.6.0

• Terragrunt now supports spin-up and tear-down commands that automatically find all the Terraform modules in the current working directory and runs terraform apply or terraform destroy in each one, in the proper order, based on their dependencies. See the docs here for details: https://github.com/gruntwork-io/terragrunt#the-spin-up-and-tear-down-commands
• Terragrunt now supports defining dependencies in the .terragrunt file to specify which other modules should be deployed before the current one. See the docs here for details: https://github.com/gruntwork-io/terragrunt#dependencies-between-modules
• You can now specify the current working directory using the --terragrunt-working-dir param. See the docs here for details: https://github.com/gruntwork-io/terragrunt#cli-options

v0.5.1

• Fix panic when an S3 bucket exists but doesn't have versioning enabled

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.