Update dependency gruntwork-io/terragrunt to v0.35.2

This MR contains the following updates:

Package	Type	Update	Change
gruntwork-io/terragrunt	ironbank-github	minor	v0.34.3 -> v0.35.2
gruntwork-io/terragrunt		minor	v0.34.3 -> v0.35.2

---

Release Notes

gruntwork-io/terragrunt

v0.35.2

Compare Source

Description

Fixed a regression bug introduced in v0.35.1 where the iam_role config was ignored when managing the s3 state bucket in auto init.

Related links

• https://github.com/gruntwork-io/terragrunt/pull/1867

v0.35.1

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-iam-role
• --terragrunt-iam-assume-role-duration
• --terragrunt-iam-assume-role-session-name
• iam_role
• iam_assume_role_duration
• iam_assume_role_session_name

Description

NOTE: There is a regression bug introduced in this version. We recommend using v0.35.2.

The following bugs related to the assume IAM role features of terragrunt has been fixed:

• There was a bug in the logic for --terragrunt-assume-role-session-name, where the default session name was always used when the CLI option was not passed in due to the session name being set on the options struct with the default. Now the default is only used if it is not explicitly set by CLI flag or config.
• There was a bug in the logic for assuming IAM roles in the remote state initialization, where it did not use the session duration or the session name that was set on the CLI. Now the remote state initialization will use the session duration and session name passed through the CLI, if set.
• There was a bug in the logic for assuming IAM roles for the terragrunt AWS internal helper functions, where it did not use the session duration or the session name from the config or CLI. Now the AWS internal helpers will use the session duration and session name if set.
• There was a bug in the logic for dependency, where it did not use the session duration or the session name from the config or CLI. Now dependency fetching will use the session duration and the session name if set.

Related links

• https://github.com/gruntwork-io/terragrunt/pull/1858

v0.35.0

Compare Source

Updated CLI args, config attributes and blocks

• dependencies [BACKWARD INCOMPATIBLE]
• dependency
• include

Description

• Fixed bug where Terragrunt only took the last include block into consideration for the dependency run graph. Now all dependency blocks defined across all include configurations will be taken into consideration.

Migration guide

As a part of this change, the behavior of how dependencies blocks are merged together in the shallow merge strategy has been updated to be a deep merge - now all the paths defined in dependencies blocks across the included modules are always concatenated together rather than replaced. If you have a configuration that depended on the old behavior, you will need to update your configuration to take advantage of multiple include blocks to selectively include the parent dependencies block.

E.g., if you had the following configurations:

parent terragrunt.hcl

dependencies {
  paths = ["../vpc", "../mysql"]
}
### ... other blocks ...

child terragrunt.hcl

include "root" {
  path = find_in_parent_folders()
}

dependencies {
  paths = ["../new_vpc"] # intended to replace dependencies block in parent
}
### ... other blocks ...

You will want to update to the following:

parent terragrunt.hcl

### ... other blocks ...

dependencies parent terragrunt.hcl

dependencies {
  paths = ["../vpc", "../mysql"]
}

child terragrunt.hcl

include "root" {
  path = find_in_parent_folders()
}

dependencies {
  paths = ["../new_vpc"] # intended to replace dependencies block in parent
}
### ... other blocks ...

child who wants dependencies

include "root" {
  path = find_in_parent_folders()
}

include "dependencies" {
  path = find_in_parent_folders("dependencies_parent_terragrunt.hcl")
}
### ... other blocks ...

Related links

• https://github.com/gruntwork-io/terragrunt/pull/1864

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this MR, check this box.

---

This MR has been generated by Renovate Bot.