Skip to content

Update dependency gruntwork-io/terragrunt to v0.85.0 #440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency gruntwork-io/terragrunt to v0.85.0 #440

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor 0.83.2 -> 0.85.0

Release Notes

gruntwork-io/terragrunt (gruntwork-io/terragrunt)

v0.85.0

Compare Source

🛠️ Breaking Changes

Removal of legacy Terragrunt flags

All deprecated flags that start with --terragrunt- have been removed in favor of their modern counterparts.

This is the next step in the removal of deprecated features in
Terragrunt on the road to Terragrunt 1.0, with more to follow. Read the CLI Redesign migration guide for future breaking changes.

Update of stack run directory context

The stack run command no longer assumes that users will have a .terragrunt-stack directory present in the same directory as the terragrunt.stack.hcl file. This caused issues for users that were leveraging the no_dot_terragrunt_stack attribute, as the run might have skipped over units generated outside the .terragrunt-stack directory and thrown an error if all units were generated without the .terragrunt-stack directory.

For the following terragrunt.stack.hcl file:

unit "foo" {
  source = "../units/foo"
  path   = "foo"

  no_dot_terragrunt_stack = true
}

unit "bar" {
  source = "../units/bar"
  path   = "bar"
}

Users would experience the following stack run output:

tg-stack-run-before

They will now get the following:

tg-stack-run-after

✨ Features

The runner-pool experiment has been integrated with OpenTelemetry

The runner-pool experiment has been updated to integrate properly with OpenTelemetry.

🐛 Bug Fixes

stack output now respects no_dot_terragrunt_stack

Previously, when running the stack output command, Terragrunt would incorrectly assume that all units were generated within a .terragrunt-stack directory. This bug has been fixed, and Terragrunt will know to look directly in the stack directory for a given unit when supplied with no_dot_terragrunt_stack.

The runner-pool experiment no longer parses stack files as units during discovery

A bug in the logic for the discovery package resulted in discovery errors due to terragrunt.stack.hcl files being parsed as units. That bug has been fixed.

Fixed filesystem context for find_in_parent_folders() when used in terragrunt.stack.hcl

The use of find_in_parent_folders() now functions correctly when run in the context of a terragrunt.stack.hcl file. Previously, it relied on the current working directory of the Terragrunt CLI, which incorrectly assumed that users would always be generating terragrunt.stack.hcl files from the current working directory.

The discovery package now emits less false positive warnings during parsing

The discovery package used by the find and list commands, and the runner-pool experiment has been updated to emit less unimportant warnings when parsing configurations. These warnings were for early phase parsing that are known to be safe to ignore.

The discovery package no longer attempts to parse stack configurations as units

A bug in the implementation of the discovery package resulted in attempts from Terragrunt to parse terragrunt.stack.hcl files as units. That has been remediated.

📖 Docs

Edit Link Added

The terragrunt-v1.gruntwork.io docs now include an "Edit page" button that conveniently allows the community to contribute fixes to documentation from within their browsers, using the GitHub UI.

image

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.84.1...v0.85.0

v0.84.1

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.84.0...v0.84.1

v0.84.0

Compare Source

🛠️ Breaking Changes

Removal of legacy-all commands

The following commands have been removed from the Terragrunt CLI:

  • spin-up
  • tear-down
  • plan-all
  • apply-all
  • destroy-all
  • output-all
  • validate-all

If you have been using any of these commands, see the migration guide under Removal of longstanding deprecated commands here.

This is the first step in the removal of deprecated features in Terragrunt on the road to Terragrunt 1.0, with more to follow. You are also advised to read the CLI Redesign migration documentation for future breaking changes.

See #​3535 for more details.

✨ New Features

Catalog/Scaffold now support --no-dependency-prompt

The catalog/scaffold commands now support a new --no-dependency-prompt flag that disables the Boilerplate dependency prompt (equivalent of --disable-dependency-prompt in Boilerplate).

This allows Boilerplate templates with dependencies to be used non-interactively, even when called by Catalog and Scaffold.

exclude block now supports no_run

The exclude block now supports the no_run attribute, which lets users prevent direct runs of a unit when the run matches the configuration of an exclude block.

e.g. When users define an exclude block like the following:

### foo/terragrunt.hcl

exclude {
    if      = true
    actions = ["plan"]
}

Terragrunt will only exclude the unit foo from the run queue if the user supplies a command like run --all plan. If a user uses the run plan command directly in the foo directory, it’s assumed that they are doing so intentionally, and don’t want the run to exit early.

Users can now specify no_run to explicitly tell Terragrunt that it should never be run, even if a user attempts to perform the run in the unit directory directly.

### foo/terragrunt.hcl

exclude {
    if      = true
    no_run  = true
    actions = ["plan"]
}

💪🏽 Enhancements

Stacks are now fully regenerated when the --source-update flag is set

The .terragrunt-stack directory is now fully regenerated when the --source-update flag is set, similar to how the .terragrunt-cache directory is regenerated when the flag is set.

This addresses some edge-cases where changes to local sources for units and stacks didn’t result in updates to generated stack configurations.

🐛 Bug Fixes
Stack Outputs Are Now Sorted

To ensure consistency in the order in which outputs are displayed when using the stack output command, outputs are now sorted before they are displayed.

Lockfiles With Strong Constraints Normalized

When manually generating lockfiles from the Provider Cache Server for modules with strong constraints like the following:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "= 5.100.0"
    }
  }
}

Generated lockfiles now properly strip the = when generating the lockfile, as = constraints aren’t supported in .terraform.lock.hcl files.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.83.2...v0.84.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.84.0 Update dependency gruntwork-io/terragrunt to v0.84.1 Aug 4, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ee8e0fe to 1d56c13 Compare August 4, 2025 16:59
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.84.1 Update dependency gruntwork-io/terragrunt to v0.85.0 Aug 15, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 1d56c13 to aa79b40 Compare August 15, 2025 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants