Skip to content

Update dependency gruntwork-io/terragrunt to v0.96.0 #451

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
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency gruntwork-io/terragrunt to v0.96.0 #451

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 9, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor 0.89.3 -> 0.96.0

Release Notes

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

v0.96.0

Compare Source

🛠️ Breaking Changes

The --no-destroy-dependencies-check flag has been deprecated

The default behavior of Terragrunt with respect to checking dependents during destroys has been inverted. As a consequence the --no-destroy-dependencies-check has been deprecated, and a new --destroy-dependencies-check flag has been introduced.

Previously, Terragrunt would automatically parse all configurations that might depend on a unit being destroyed to warn users that the destroyed configuration might orphan other units that depend on it. This was frequently undesirable behavior due to the fact that it introduced additional unnecessary work (parsing all HCL configurations unnecessarily), and could introduce errors if users had unrelated invalid HCL configurations.

Terragrunt now requires that users opt-in to this behavior via the new --destroy-dependencies-check flag, which enables the destroy check, and will not perform the destroy check by default.

terragrunt run --destroy-dependencies-check -- destroy

To learn more, see the no-destroy-dependencies-check strict control.

The --disable-command-validation flag has been deprecated

Terragrunt no longer performs command name validation when passing commands to OpenTofu/Terraform from Terragrunt when using the run command. This makes the --disable-command-validation flag unnecessary, as the lack of validation is now the default behavior.

Previously, Terragrunt had no way to explicitly indicate that a command being used on the Terragrunt CLI was intended as a passthrough to the OpenTofu/Terraform CLI, so it was important that validation be done on the command being supplied on the Terragrunt CLI.

Since completion of the CLI Redesign, this has changed significantly. Users now have explicit shortcuts on the Terragrunt CLI for common OpenTofu/Terraform commands and an explicit interface for passing through OpenTofu/Terraform commands to the OpenTofu/Terraform CLIs using the run command. By removing this validation, Terragrunt will now automatically support new OpenTofu/Terraform commands in future versions of the tools and allow for greater flexibility in IaC Engines, as novel commands can be introduced.

To learn more, see the disable-command-validation strict control.

The --experimental-engine flag now enables the iac-engine experiment

The experimental IaC Engine feature was introduced in Terragrunt prior to the introduction of the experiment system. As such, it wasn’t enabled when users enabled experiment mode, and didn’t have a dedicated section in the experiments docs.

The --experimental-engine flag is now an alias for explicitly enabling the iac-engine experiment, and using IaC Engines will be allowed when using Terragrunt in experiment mode. This increases consistency with how experimental features are managed in Terragrunt, and reduces the surface area users have to be aware of in the Terragrunt CLI.

terragrunt run --experiment=iac-engine

Note that you can explicitly disable usage of engines now with the --no-engine flag, even when the experiment is active.

terragrunt run --experiment=iac-engine --no-engine

To learn more, see the iac-engine experiment.

The --dependency-fetch-output-from-state flag now enables the dependency-fetch-output-from-state experiment

The experimental —dependency-fetch-output-from-state flag was introduced in Terragrunt prior to the introduction of the experiment system. As such, it wasn’t enabled when users enabled experiment mode, and didn’t have a dedicated section in the experiments docs.

The --dependency-fetch-output-from-state flag is now an alias for explicitly enabling the dependency-fetch-output-from-state experiment, and Terragrunt will automatically attempt to fetch outputs from backend state when in experiment mode. This increases consistency with how experimental features are managed in Terragrunt, and reduces the surface area users have to be aware of in the Terragrunt CLI.

terragrunt run --experiment=dependency-fetch-output-from-state

Note that you can explicitly disable fetching output from state with the --no-dependency-fetch-output-from-state flag, even when the experiment is active.

terragrunt run --experiment=dependency-fetch-output-from-state --no-dependency-fetch-output-from-state

To learn more, see the dependency-fetch-output-from-state experiment.

🧪 Experiments Updated

The filter-flag experiment now supports the --filters-file flag

The --filters-file flag has been introduced to allow for the application of multiple filters as defined in a newline-delimited text file, similar to the existing --excludes-file flag (remember that you must use the filter-flag experiment to try this).

 # custom-filters.txt
 !./unstable/**
 $ terragrunt find --filters-file custom-filters.txt
 # No results in `./unstable` discovered.

When the filter-flag experiment is active, Terragrunt will automatically parse and apply filters found in a .terragrunt-filters file, similar to how it automatically parses and applies excludes found in a .terragrunt-excludes file.

 # .terragrunt-filters
 !./unstable/**
# Note that it only does this by default when the experiment is active.
terragrunt find

# Still no results in `./unstable` discovered.

To explicitly disable usage of filter files (including the automatic .terragrunt-filters file), use the --no-filters-file flag.

 # .terragrunt-filters
 !./unstable/**
# Note that it only does this by default when the experiment is active.
terragrunt find --no-filters-file

# This _will_ allow results in `./unstable` to be discovered.

Unlike the --excludes-file, usage of the --filters-file flag also allows for always filtering for particular configurations.

# .terragrunt-filters
./always-include/**

To learn more, see the filters file documentation.

🐛 Bug Fixes

Unnecessary .terragrunt-cache directory no longer generated in run --all runs

Fixed a regression where run --all would create empty .terragrunt-cache directories in the current working directory, even when not needed.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.95.1...v0.96.0

v0.95.1

Compare Source

🧪 Experiments Updated

The filter-flag experiment now supports the --filter-affected flag

The --filter-affected flag has been introduced as an convenience alias for --filter [main...HEAD] (remember that you must use the filter-flag experiment to try this).

terragrunt find --filter-affected

Note that if you have local Git configurations that results in a different branch being your default branch, that branch will be used instead of main.

🐛 Bug Fixes

Integration of --queue-strict-include with --queue-include-units-reading fixed

A regression in --queue-strict-include resulted in empty run queues when using a combination of --queue-strict-include with --queue-include-units-reading. That bug has been resolved.

Integration of --source with run --all fixed

A regression in --source prevented it from working correctly in combination with run --all , resulting in empty run queues. That bug has been resolved.

Integration of Git-expressions with explicit stacks

A bug in the implementation of explicit stack generation for Git-expressions prevented stacks from being generated in Git worktrees when using Git-expressions in the filter-flag experiment. That bug has been resolved.

🧹 Chores

Dependencies updates
  • cloud.google.com/go/storage —> v1.58.0
  • github.com/aws/aws-sdk-go-v2 —> v1.41.0
  • github.com/hashicorp/go-version —> v1.8.0
  • github.com/aws/smithy-go —> v1.24.0

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.95.0...v0.95.1

v0.95.0

Compare Source

🛠️ Breaking Changes

The --queue-exclude-external flag has been deprecated

Previously, Terragrunt would automatically pull in external dependencies (dependencies outside the current working directory when running terragrunt run --all) into the run queue.

To prevent this behavior, users had to manually supply the --queue-exclude-external flag. This has caused significant confusion and unexpected behavior for users over the duration of it’s existence in the Terragrunt CLI. To prevent this unexpected behavior for users and follow the principle of least surprise, this flag has been deprecated and its behavior is now the default in Terragrunt.

To explicitly request inclusion of external dependencies in the run queue, use the —queue-include-external flag.

⚙️ Process Updates

OpenTofu 1.11.x added to compatibility matrix

We are now continuously testing against OpenTofu 1.11.1 in our Continuous Integration testing, and have updated the compatibility matrix to reflect that.

🧪 Updated Experiments

The filter-flag experiment now supports Git-based expressions

The --filter flag can now be used to filter units based on changes in Git history (remember that you must use the filter-flag experiment to try this).

# Compare between two references
terragrunt find --filter '[main...HEAD]'

# Shorthand: compare reference to HEAD
terragrunt find --filter '[main]'

# Compare between specific commits
terragrunt find --filter '[abc123...def456]'

# Compare between tags
terragrunt find --filter '[v1.0.0...v2.0.0]'

# Compare using relative references
terragrunt find --filter '[HEAD~1...HEAD]'

# Compare between branches
terragrunt find --filter '[feature-branch...main]'

For more information, see the dedicated documentation on Git-Based Filtering.

🐛 Bug Fixes

Units now properly flush stdout in run --all

A regression in unit stdout flushing caused stdout for unit logs to hang pending resolution of run --all runs. This regression has been fixed to ensure that logs are streamed in real time again.

Queue entries now properly run, even if dependent units are excluded

A bug in run queue optimization made it so that excluding the dependent of a unit within a multi-unit run queue would incorrectly exclude the dependency unit from the run queue. This bug has been resolved, and units are now properly included, even if their dependents are excluded.

Provider cache server only contacts relevant registries

The provider cache server was incorrectly establishing a connection with multiple registries even though only one registry for a given IaC tool run by Terragrunt. For users with network-restricted environments, this could cause problems. Terragrunt will now only contact the relevant registry for a given IaC tool unless users explicitly request for usage of multiple registries.

📖 Documentation Updates

Provider cache server no longer documented as experimental

The Provider Cache Server has been used in production by a good portion of the Terragrunt community based on voluntary community reporting. The need for the feature is also mitigated by advances in OpenTofu that makes the Automatic Provider Cache Dir the default solution all Terragrunt users using OpenTofu ≥ v1.10.0.

As such, the Provider Cache Server has been promoted to a generally available feature that is exclusively opt-in for users that cannot benefit from the Automatic Provider Cache Dir feature, or are better served by the Provider Cache Server due to scale or platform limitations.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.94.0...v0.95.0

v0.94.0

Compare Source

✨ Features

  • Terraform 1.14: We are now testing Terragrunt against Terraform 1.14 and is confirmed to be working.

NOTE: Although this release is marked as backward incompatible, it is functionally compatible as nothing has been changed in Terragrunt internals. The minor version release is useful to mark the change in Terraform version that is being tested.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.13...v0.94.0

v0.93.13

Compare Source

🐛 Bug Fixes

Catalog module source URL construction

Fixed malformed version-pinned catalog module URLs where TerraformSourcePath() incorrectly placed //moduleDir after ?ref=, ensuring correct root and submodule URL formatting.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.12...v0.93.13

v0.93.12

Compare Source

🐛 Bug Fixes

False positive errors during dependent units discovery

Reduced false-positive log messages emitted while discovering dependent units during destroy operations.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.11...v0.93.12

v0.93.11

Compare Source

🐛 Bug Fixes

Stack files matching

Fixed stack detection so only files whose base name exactly matches the default stack name are treated as stack files.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.10...v0.93.11

v0.93.10

Compare Source

🐛 Bug Fixes

Handling of disabled units in discovery

Discovery now skips units that are marked as disabled.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.9...v0.93.10

v0.93.9

Compare Source

✨ New Features

Added support for Openbao encryption provider

Key provider now supports openbao

🐛 Bug Fixes

Fixed error in calling sensitive() function in HCL

HCL sensitive() function now correctly handles values and calls without errors.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.8...v0.93.9

v0.93.8

Compare Source

⚙️ Process Improvements

Terragrunt static executables
  • Release pipeline now publishes statically linked executables

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.7...v0.93.8

v0.93.7

Compare Source

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.93.6...v0.93.7

v0.93.6

Compare Source

⚙️ Process Improvements

Terragrunt release automation moved to GitHub Actions

The release automation for Terragrunt has moved to GitHub Actions. With this move, Terragrunt releases now support:

  • Windows binary signing
  • Additional packaging for artifacts (.zip and .tar.gz release artifacts)

You can still download standalone executables from release assets for backward compatibility.

🧪 Experiments Updated

The filter-flag experiment now supports the source= attribute

The --filter flag can now be used to filter units by their usage of particular OpenTofu/Terraform modules in their terraform source blocks (remember that you must use the filter-flag experiment to try this).

# Filter by exact source match
terragrunt find --filter 'source=github.com/acme/foo'
terragrunt find --filter 'source=gitlab.com/example/baz'
terragrunt find --filter 'source=./module'

# Filter by source using glob patterns
terragrunt find --filter 'source=*github.com**acme/*'
terragrunt find --filter 'source=git::[email protected]:acme/**'
terragrunt find --filter 'source=**github.com**'
terragrunt find --filter 'source=gitlab.com/**'

For more information, see the filter feature documentation.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.5...v0.93.6

v0.93.5

Compare Source

🧪 Experiments Updated

The filter-flag experiment now supports --filter in stack generate

The --filter flag can now be used in the stack generate command, and any command that performs stack generation, e.g. run --all (remember that you must use the filter-flag experiment to try this).

The --filter flag works in a slightly unique way when used to control stack generation in that it needs to be explicitly restricted to stacks for it to impact stack generation using the type=stack attribute filter.

e.g.

# Supported: Only generate the stacks that match the filter, as we are explicitly indicating that we are targeting stacks.
terragrunt stack generate --filter 'name=prod | type=stack'

# Not supported: This filter will be ignored, as we are not explicitly indicating that we are targeting stacks.
terragrunt stack generate --filter 'name=prod'  # This will not work

The reason for this is that stack generation can also be done automatically as part of other commands, like run, and thus we need to make it clear that we’re trying to control stack generation rather than run behavior.

# This will run any unit named 'vpc'
terragrunt run --all --filter 'vpc' -- plan

# This will run any unit named 'vpc', and prevent stack generation in any stack not named 'dev' (including any stacks named 'vpc')
terragrunt stack run --filter 'vpc' --filter 'name=dev | type=stack' -- apply

For more information, see the filter feature documentation

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.4...v0.93.5

v0.93.4

Compare Source

🧪 Updated Experiments

The filter-flag experiment now supports graph expressions

The --filter flag now supports usage of graph expressions, allowing users to filter based on the dependency relationship of units discovered by Terragrunt (remember that you must use the filter-flag experiment to try this).

e.g.

# Find 'service' and everything it depends on
terragrunt find --filter 'service...'

# Find 'vpc' and everything that depends on it
terragrunt find --filter '...vpc'

# Find 'db' and its complete dependency graph
terragrunt find --filter '...db...'

# Find all dependents of 'vpc' but exclude 'vpc' itself
terragrunt find --filter '...^vpc'

You can learn more about graph-based filtering in the filter feature documentation.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.3...v0.93.4

v0.93.3

Compare Source

🐛 Bug Fixes

hcl validate --inputs regression on validation blocks resolved

A bug introduced in v0.93.1 preventing hcl validate --inputs from succeeding on OpenTofu/Terraform modules with variables containing validation blocks. This was caused by an error in the update to OpenTofu/Terraform .tf file parsing by Terragrunt in the hcl validate command.

That bug has been resolved.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.2...v0.93.3

v0.93.2

Compare Source

✨ New Features

The list command now supports the dot fomat

The list command can now render its output in the Graphviz DOT language:

$ terragrunt list --format=dot --dependencies
digraph {
  "live/dev/vpc" ;
  "live/dev/db" ;
  "live/dev/ec2" ;
  "live/dev/db" -> "live/dev/vpc";
  "live/dev/ec2" -> "live/dev/db";
  "live/dev/ec2" -> "live/dev/vpc";
  "live/prod/vpc" ;
  "live/prod/db" ;
  "live/prod/ec2" ;
  "live/prod/db" -> "live/prod/vpc";
  "live/prod/ec2" -> "live/prod/db";
  "live/prod/ec2" -> "live/prod/vpc";
}

This was previously only possible using the dag graph command, but that command has been refactored to be an alias for the list --format=dot --dependencies command, to provide greater flexibility in how graphs are rendered in the DOT language. This includes integration with the experimental Filter feature.

You can learn more about this in the list command documentation

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.1...v0.93.2

v0.93.1

Compare Source

🏎️ Performance Improvements

  • Reduced redundant --auth-provider-cmd invocations during run-all
  • This cuts down on external credential calls and lowers authentication overhead for large runs.
  • Updated the unit resolver to reuse the configuration parsed during discovery instead of re-parsing each terragrunt.hcl.
  • This reduces HCL parses and allocations, shortening execution time on complex stacks.

In our internal “Run all with Auth Provider” benchmark (10 runs, ~10 ms on auth command), these changes reduced average runtime from ~235 ms to ~213 ms (about 9% faster) compared to v0.93.0.

Benchmarks of "BenchmarkDependencyPairwiseOddDependsOnPrevEvenRandomWait" release changes vs main

509178299-daaabc37-3834-40a4-95b3-19a2fb5f2c6d

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.93.0...v0.93.1

v0.93.0

Compare Source

🛠️ Breaking Changes

Removal of deprecated HCL attributes

The skip, retryable_errors, retry_max_attempts and retry_sleep_interval_sec have all been removed from Terragrunt.

This is the final planned breaking change on the road to Terragrunt 1.0 related to removal of deprecated functionality. Breaking changes will be minimized before Terragrunt 1.0, but may still occur based on user feedback, or based on the need to stabilize parts of Terragrunt before 1.0.

If you are currently using the skip attribute, you'll want to adjust your usage to leverage the exclude block instead:

Before:

# terragrunt.hcl

skip = true

After:

# terragrunt.hcl

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

If you are currently using the retryable_errors attribute, you'll want to adjust your usage to leverage the errors block instead:

Before:

# terragrunt.hcl

retryable_errors = [
  ".*Error: transient network issue.*",
  ".*Error: timeout.*"
]

retry_max_attempts     = 3
retry_sleep_interval_sec = 5

After:

# terragrunt.hcl

errors {
  retry "transient_errors" {
    retryable_errors = [
      ".*Error: transient network issue.*",
      ".*Error: timeout.*"
    ]
    max_attempts = 3
    sleep_interval_sec = 5
  }
}

Read the detailed migration guide for more information.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.92.1...v0.93.0

v0.92.1

Compare Source

✨ New Features

hcl fmt supports --parallelism for controlling concurrency

The hcl fmt command now supports the --parallelism flag for controlling the number of concurrent files getting formatted. By default, the number of concurrent file formats will be determined by the number of CPU cores detected on the system running Terragrunt.

See hcl fmt documentation for more information.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.92.0...v0.92.1

v0.92.0

Compare Source

🛠️ Breaking Changes

Internal boilerplate dependency upgraded to v0.10.1

The templating engine (Boilerplate) used by the Terragrunt catalog and scaffold commands has been upgraded to v0.10.1.

As a consequence, the default behavior of scaffolding when using the catalog and scaffold commands has changed to allow for the use of Boilerplate hooks and shell commands (see hooks and helpers in Boilerplate documentation) by default.

Note that Boilerplate will ask for permission interactively by default to run said hooks and shell commands, and that the interactive prompt will propagate to Terragrunt users.

e.g.

$ terragrunt scaffold github.com/gruntwork-io/terragrunt//test/fixtures/scaffold/with-shell-commands
...
[boilerplate] 2025/10/24 13:44:56 Shell command details:
[boilerplate] 2025/10/24 13:44:56   Command: echo
[boilerplate] 2025/10/24 13:44:56   Arguments: [-n SHELL_EXECUTED_VALUE_1]
[boilerplate] 2025/10/24 13:44:56   Working Directory: /var/folders/x3/j561187d7bn7j25xf6hs73wr0000gn/T/scaffold3587887181/.boilerplate
Execute shell command? (y/a/n) :
$ terragrunt scaffold github.com/gruntwork-io/terragrunt//test/fixtures/scaffold/with-hooks
...
[boilerplate] 2025/10/24 13:48:27 Hook details:
[boilerplate] 2025/10/24 13:48:27   Command: echo
[boilerplate] 2025/10/24 13:48:27   Arguments: [BEFORE_HOOK_EXECUTED]
[boilerplate] 2025/10/24 13:48:27   Working Directory: /var/folders/x3/j561187d7bn7j25xf6hs73wr0000gn/T/scaffold4203613613/.boilerplate
Execute hook? (y/a/n) :

When using the --non-interactive flag, Terragrunt will skip prompts and allow hooks and shell commands automatically by default.

$ terragrunt scaffold github.com/gruntwork-io/terragrunt//test/fixtures/scaffold/with-hooks --non-interactive
...
[boilerplate] 2025/10/24 13:50:56 Executing hook (previously confirmed or all confirmed)
[boilerplate] 2025/10/24 13:50:56 Running command: echo BEFORE_HOOK_EXECUTED
BEFORE_HOOK_EXECUTED
...
[boilerplate] 2025/10/24 13:50:56 Executing hook (previously confirmed or all confirmed)
[boilerplate] 2025/10/24 13:50:56 Running command: echo AFTER_HOOK_EXECUTED
AFTER_HOOK_EXECUTED

If you would like to explicitly prevent this behavior, you can use the --no-hooks and --no-shell flags added to catalog and scaffold to explicitly prevent usage of these features:

$ terragrunt scaffold github.com/gruntwork-io/terragrunt//test/fixtures/scaffold/with-hooks --non-interactive --no-hooks --no-shell
...
[boilerplate] 2025/10/24 13:53:40 Hooks are disabled, skipping 1 hook(s)
...
[boilerplate] 2025/10/24 13:53:40 Hooks are disabled, skipping 1 hook(s)
13:53:40.141 INFO   Running fmt on generated code .
13:53:40.143 INFO   Scaffolding completed
$ terragrunt scaffold github.com/gruntwork-io/terragrunt//test/fixtures/scaffold/with-shell-commands --non-interactive --no-hooks --no-shell
...
[boilerplate] 2025/10/24 13:54:47 Shell helpers are disabled. Will not execute shell command '[echo -n SHELL_EXECUTED_VALUE_1]'. Returning placeholder value 'replace-me'.
[boilerplate] 2025/10/24 13:54:47 Shell helpers are disabled. Will not execute shell command '[echo -n SHELL_EXECUTED_VALUE_2]'. Returning placeholder value 'replace-me'.
[boilerplate] 2025/10/24 13:54:47 Hooks are disabled, skipping 0 hook(s)
13:54:47.356 INFO   Running fmt on generated code .
13:54:47.356 INFO   ./terragrunt.hcl was updated
13:54:47.356 INFO   Scaffolding completed

You can also set the no_hooks and no_shell attributes in your catalog config to have these set by default for all users of your project:

# root.hcl
catalog {
  no_shell = true
  no_hooks = true
}

⚠️ Remember that IaC configurations are inherently powerful, and should not be trusted blindly. Make sure that you review and trust template sources when generating templates using Terragrunt.

🧪 Experiments Updated

filter-flag experiment now supported in hcl commands

The --filter flag is now supported in hcl commands (validate and fmt) (remember that you must use the filter-flag experiment to try this).

e.g.

# Filter by path with glob patterns
terragrunt hcl validate --filter './prod/**'

# Filter by name
terragrunt hcl validate --filter 'app*'

# Exclude specific configurations
terragrunt hcl validate --filter '!./test/**'

# Combine filters with intersection (refinement)
terragrunt hcl validate --filter './prod/** | !name=legacy'

# Multiple filters with union
terragrunt hcl validate --filter 'app1' --filter 'app2'

When using the --filter flag for hcl fmt, filtering applies to files instead of units / stacks. Only file path filters are supported for the hcl fmt command.

# Format a particular file
terragrunt hcl fmt --filter './prod/app1/terragrunt.hcl'

# Format files matching a glob
terragrunt hcl fmt --filter './prod/**'

# Exclude specific configurations
terragrunt hcl fmt --filter '!./test/**'

🏎️ Performance Improvements

hcl fmt Performance Improved

The performance of the hcl fmt command has been improved substantially.

Screenshot 2025-10-27 at 10 15 56

Formatting files is now roughly twice as fast due to parallelization of file formatting, and optimizations used in file exclusion.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.91.5...v0.92.0

v0.91.5

Compare Source

🧪 Experiments Updated

filter-flag updated with run support

The --filter flag is now supported on the run command (remember that you must use the filter-flag experiment to try this).

e.g.

# Filter by path with glob patterns
terragrunt run --all --filter 'prod/**' -- plan

# Filter by name
terragrunt run --all --filter 'app*' -- apply

# Exclude specific configurations
terragrunt run --all --filter '!./test/**' -- plan

# Combine filters with intersection (refinement)
terragrunt run --all --filter './prod/** | !name=legacy' -- apply

# Multiple filters with union
terragrunt run --all --filter 'app1' --filter 'app2' -- plan

For more information, see the documentation on Filtering Units.

If you give this feature a try, make sure to share your feedback on the Filter Flag RFC

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.91.4...v0.91.5

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 force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 9895e30 to ba46cce Compare October 10, 2025 17:06
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.89.4 Update dependency gruntwork-io/terragrunt to v0.90.0 Oct 10, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ba46cce to e4fd59e Compare October 15, 2025 15:43
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.90.0 Update dependency gruntwork-io/terragrunt to v0.90.1 Oct 15, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.90.1 Update dependency gruntwork-io/terragrunt to v0.91.0 Oct 15, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from e4fd59e to cc2e9c9 Compare October 15, 2025 18:53
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.91.0 Update dependency gruntwork-io/terragrunt to v0.91.1 Oct 16, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from cc2e9c9 to cfe31bf Compare October 16, 2025 22:29
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.91.1 Update dependency gruntwork-io/terragrunt to v0.91.2 Oct 20, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 99a33da to 573f069 Compare October 23, 2025 17:39
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.91.2 Update dependency gruntwork-io/terragrunt to v0.91.4 Oct 23, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.91.4 Update dependency gruntwork-io/terragrunt to v0.91.5 Oct 24, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 9d5f81c to 6351ff1 Compare October 27, 2025 17:53
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.91.5 Update dependency gruntwork-io/terragrunt to v0.92.0 Oct 27, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 6351ff1 to 2c6e382 Compare October 28, 2025 22:48
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.92.0 Update dependency gruntwork-io/terragrunt to v0.92.1 Oct 28, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2c6e382 to 09bf67d Compare October 31, 2025 20:09
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.92.1 Update dependency gruntwork-io/terragrunt to v0.93.0 Oct 31, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 09bf67d to c2d09e2 Compare November 4, 2025 23:05
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.0 Update dependency gruntwork-io/terragrunt to v0.93.1 Nov 4, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c2d09e2 to 5098d62 Compare November 5, 2025 19:52
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.1 Update dependency gruntwork-io/terragrunt to v0.93.3 Nov 5, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 5098d62 to 66cda26 Compare November 11, 2025 02:44
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.3 Update dependency gruntwork-io/terragrunt to v0.93.5 Nov 11, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 66cda26 to 943fa91 Compare November 12, 2025 01:43
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.5 Update dependency gruntwork-io/terragrunt to v0.93.6 Nov 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 943fa91 to 6d67f74 Compare November 12, 2025 19:51
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.6 Update dependency gruntwork-io/terragrunt to v0.93.8 Nov 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 6d67f74 to 8960132 Compare November 17, 2025 18:01
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.8 Update dependency gruntwork-io/terragrunt to v0.93.9 Nov 17, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 8960132 to 2e21e7a Compare November 20, 2025 17:55
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.9 Update dependency gruntwork-io/terragrunt to v0.93.10 Nov 20, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2e21e7a to 861c60f Compare November 24, 2025 20:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.10 Update dependency gruntwork-io/terragrunt to v0.93.11 Nov 24, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 861c60f to e343930 Compare December 1, 2025 19:53
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.11 Update dependency gruntwork-io/terragrunt to v0.93.12 Dec 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from e343930 to a41cd94 Compare December 5, 2025 21:24
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.12 Update dependency gruntwork-io/terragrunt to v0.93.13 Dec 5, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.93.13 Update dependency gruntwork-io/terragrunt to v0.94.0 Dec 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from ae4ad19 to dd8571a Compare December 12, 2025 14:58
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.94.0 Update dependency gruntwork-io/terragrunt to v0.95.0 Dec 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from dd8571a to be704ed Compare December 12, 2025 22:48
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.95.0 Update dependency gruntwork-io/terragrunt to v0.95.1 Dec 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from be704ed to a8948f1 Compare December 15, 2025 22:02
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.95.1 Update dependency gruntwork-io/terragrunt to v0.96.0 Dec 15, 2025
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