v1.3.0

Make apply requirements always appear in output.

v1.2.1

Merged: #124

Added a new flag, --filter, to restrict which terragrunt.hcl files have projects generated for them

v1.2.0

Before this change, this module determined if a terragrunt.hcl file was a parent or not by examining if it had a terraform.source field in it's hcl. This is not enough, as some actual (non-parent) modules may leave this field blank, which assumes a default of terraform { source = "." }.

This change now also looks if there is an includes block present, which is a definite signal that a module is not a parent.

v1.1.1

Taken from #113:

Fix issue with parsing for a cascading dependencies case, Fix Duplicated dependencies, Handle Relative/Absolute Paths more gracefully #113

Improvement: In order to fix the issue with cascading dependencies this adds extra checks to handle both the case that a dependency uses an absolute path or a relative one.

Improvement: Also converts relative dependencies to absolute to avoid duplicates and re-converts the dependencies to a relative before the configuration file is generated.

Fix issue with parsing for a cascading dependencies case
Creates new terragrunt options with the dependency path in order to be able to parse successfully the cascading dependencies.

v1.1.0

Adds support for using apply_requirements in the terragrunt config.

These can be set in three ways:

Using a flag
You can use --apply-requirements in your generate command to set defaults that will apply to all modules

Using a local in the parent config
You can set the local atlantis_apply_requirements in your parent config to override all modules that inherit from that parent. This config is not additive to the --apply-requirements flag, but overrides the array entirely

Using a local in the child config
You can set the local atlantis_apply_requirements in your child config to override the setting for a single module. This config is not additive to the --apply-requirements flag or the local in the parent config, but overrides the array entirely

v1.0.1

Fix the terragrunt-atlantis-config version command to have the up to date version present

v1.0.0

First major release 🎉

The primary upgrade here is that terragrunt-atlantis-config now integrates directly into your Atlantis server, so that you and your developers do not need to install this tool onto your local machines if you don't want to. To get started with the integration, follow the instructions here: https://github.com/transcend-io/terragrunt-atlantis-config#integrate-into-your-atlantis-server

This is also a great opportunity for this library to get onto true semantic versioning. To make good use of a major version bump, there is one breaking change:

The --ignore-parent-terragrunt flag now defaults to true, while it previously defaulted to false. So if you want to create Atlantis projects for your parent configs, but previously were relying on the default, you'll need to add --ignore-parent-terragrunt=false to your commands.

v0.13.0

Before this release, if we had the dependency tree of modules

A -> B -> C

And module C is updated, only module B knows that C was updated, but we really want module A to know that C was updated as well.

This release will also state that module A depends on module C by default.

It can be optionally controlled by the flag --cascade-dependencies, which defaults to true.

v0.12.0

added a new flag, --automerge, which is documented in the README

v0.11.0

Added support for a few new features:

• a locals value atlantis_skip that will remove a module from the output
• a flag/locals combo for terraform-version to override the terraform version for some modules

Also updated the documentation a fair amount to clarify using flags and locals.