Skip to content

Comments

Update dependency terragrunt to v0.99.4#452

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/terragrunt-0.x
Open

Update dependency terragrunt to v0.99.4#452
renovate[bot] wants to merge 1 commit intomainfrom
renovate/terragrunt-0.x

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
terragrunt minor 0.89.3 → 0.99.4

Release Notes

gruntwork-io/terragrunt (terragrunt)

v0.99.4

Compare Source

🏎️ Performance Improvements

Discovery performance improved

The way in which Terragrunt discovers and filters units and stacks for runs has improved significantly.

Screenshot 2026-02-17 at 17 43 55 Screenshot 2026-02-17 at 17 44 29 Screenshot 2026-02-17 at 17 44 48

Terragrunt is now better at avoiding parsing units/stacks unnecessarily, based on the filter you use. Previously, the logic used was more coarse, and could result in a requirement to parse some configurations (e.g. presence of a dependency graph expression to result in parsing all configurations. Discovery has been refactored to allow for much more careful opt-in parsing based on the need to support the filter used by users (or lack thereof).

This will also result in improvements to Terragrunt’s ability to ignore broken parts of infrastructure estates when Terragrunt can predictably determine that it won’t impact a run.

🐛 Bug Fixes

Invalid unit configurations cause explicit errors instead of silently being excluded during runs

A bug in discovery logic resulted in units with invalid HCL configurations being silently excluded from runs with a warning. This bug has been fixed, and attempting to parse invalid HCL configurations during a run will result in an error.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.99.3...v0.99.4

v0.99.3

Compare Source

🐛 Bug Fixes

Over-warning on strict controls prevented

Using --strict-mode resulted in over-warning on completed controls. Those warnings will no longer appear when using strict mode.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.99.2...v0.99.3

v0.99.2

Compare Source

🐛 Bug Fixes

Interrupt signal propagation to OpenTofu/Terraform fixed

The mechanism by which Terragrunt sends interrupt signals to OpenTofu/Terraform processes it started has been made more robust. Terragrunt will now send the interrupt signal in the event that a user explicitly sends an interrupt signal to Terragrunt in addition to scenarios where Terragrunt’s context cancellation is triggered (e.g. in the event of a timeout).

SOPS decryption race condition fixed

A race condition in the concurrent access to SOPS decrypted secrets in different environments combined with usage of the --auth-provider-cmd flag resulted in authentication failures. Synchronization controls have been introduced to ensure authentication proceeds correctly for each environment independently.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.99.1...v0.99.2

v0.99.1

Compare Source

🐛 Bug Fixes

Pass through null inputs

Fixes a bug where null inputs weren't being passed through correctly to OpenTofu/Terraform.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.99.0...v0.99.1

v0.99.0

Compare Source

🛠️ Breaking Changes

Undocumented behavior removed

We have removed several undocumented features that served as temporary stop-gaps to facilitate experimentation.

The following environment variables no longer affect Terragrunt behavior:

  • TERRAGRUNT_TEMP_QUOTE_NULL
  • TMP_UNDOCUMENTED_REPORT_PADDER
  • TMP_UNDOCUMENTED_REPORT_UNIT_COLORIZE
  • TMP_UNDOCUMENTED_COLORIZE_DEFAULT_SUMMARY_PADDING
Internal tflint deprecated

Terragrunt has been shipping with a version of tflint compiled into the binary to allow for more convenient usage without installing tflint directly. However due to the adoption of a BUSL license in tflint, the version included in Terragrunt was frozen.

We have now deprecated use of the internal tflint hook, and will be fully removing it in the future. We still do work to integrate with tflint; Including automatically running tflint init and passing through variables. For now using the internal version will only emit a warning, and you can opt in to the future behavior today in one of two ways:

  • The legacy-internal-tflint strict control (recommended)

  • Adding the --terragrunt-external-tflint flag to your hook usage (this also works in previous versions of Terragrunt); this flag is stripped prior to running the external tflint. Example:

    terraform {
    before_hook "tflint" {
    commands = ["apply", "plan"]
    execute = ["tflint", "--terragrunt-external-tflint", "--minimum-failure-severity=error", "--config", "custom.tflint.hcl"]
  }
}

✨ New Features

Depth control for dependency traversal

Graph-based expressions in the --filter flag now support limiting the depth of graph traversal they perform when discovering units. You can now append/prepend a number to the end of a graph expression ellipsis to control how deep in graph traversal Terragrunt will look for dependents/dependencies.

e.g.

# Find 'service' and only its direct dependencies (1 level deep)
terragrunt find --filter 'service...1'

# Find 'vpc' and only components that directly depend on it (1 level)
terragrunt find --filter '1...vpc'

# Find 'db' with 2 levels of dependencies and 1 level of dependents
terragrunt find --filter '1...db...2'

This delivers major performance gains for large dependency graphs.

Special thanks to @​sofianedjerbi for contributing this feature!

Run report schema extended

The run report has been extended to include the Ref, Cmd and Args fields when relevant to a run.

  • The Ref field will be populated for runs performed in Git worktrees due to their discovery from a Git-based expression in a filter.
  • The Cmd field will contain the sub command of OpenTofu/Terraform executed in a run (e.g. plan , apply) and the Args field will contain the arguments passed to that subcommand (e.g. -auto-approve, -destroy). These can differ between runs when using Git-based expressions, as additions or modifications of units between Git references can result in a plan or apply, whereas removal of units can result in plan -destroy or apply -destroy .

🧪 Experiments Updated

IaC Engines Updated to use v0.1.0 of terragrunt-engine-go

The iac-engine experiment has been updated to use v0.1.0 of the terragrunt-engine-go library.

Given that this is still experimental functionality, no effort has been made to maintain backwards compatibility with existing engines. If you are currently using the OpenTofu engine, you will need to upgrade to v0.1.0 of the engine. The Terraform engine will be updated in the near future.

This update pulls in changes to the protobuf schema used in communication between Terragrunt and IaC engines to give engines the ability to log messages in Terragrunt and reduces the overall size of messages passed to Terragrunt for stdout/stderr messages.

⚙️ Process Updates

Curl to Bash script available

In addition to all the other installation mechanisms available to install Terragrunt, a convenient curl to bash script has been added to minimize the friction in installing and getting started with Terragrunt, and removing any dependency on third party tools if you don’t want to use them.

curl -sL https://terragrunt.gruntwork.io/install | bash

The installation can be customized, with full customization options available via the --help flag.

curl -sL https://terragrunt.gruntwork.io/install | bash -s -- --help

In addition to providing this script, the ASDF plugin for Terragrunt has been updated to automatically perform signature verification on an opt-out basis for any version of Terragrunt equal or newer to v0.98.0. The Terragrunt entry in the Aqua registry has been updated to do the same, meaning mise users will automatically benefit from this as well.

If you don’t want to use the curl to bash script, or any of the other distribution methods available, the instructions for performing signature verification manually have been updated in the installation documentation as well.

📖 Documentation Updates

OpenTofu/Terraform compatibility matrix now available as API

In addition to providing a compatibility matrix in the Supported Versions documentation, compatibility verification is also available via an API endpoint here:

https://terragrunt.gruntwork.io/api/v1/compatibility

See the compatibility API documentation for more details, including availability of query string parameters for filtering responses.

JSON schema for --auth-provider-cmd published

A JSON schema has been published for the schema expected for the stdout of commands invoked using --auth-provider-cmd. You can access the schema here.

You can use tools like this JSON schema validator or other simple utilities to programmatically validate that the stdout of JSON responses in your commands invoked by --auth-provider-cmd obey the expected schema.

🐛 Bug Fixes

Exit Codes for run --all more consistent

Fixed an issue where run --all incorrectly returned a 0 exit code when individual units failed.

Automatic retry for provider queries

To address intermittent errors in queries to the OpenTofu/Terraform provider registries, we expanded the automatic retry logic to include timeouts from provider registries.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.98.0...v0.99.0

v0.98.0

Compare Source

✨ New Features

The --filter flag now implies --all

When using the --filter flag, it is now optional to also supply --all. Terragrunt will automatically set the --all flag when you use the --filter flag.

🐛 Bug Fixes

Plan files are now correctly passed as CLI arguments for destroy operations

A bug in the logic used for injecting plan files as arguments to the apply -destroy command resulted in the plan file argument being injected prior to the -auto-approve flag, which is disallowed in OpenTofu/Terraform. That bug has been fixed.

GCS bootstrap authentication fixed

A bug in the authentication logic for GCS backends prevented successful bootstrapping of backends when using the --auth-provider-cmd flag. That bug has been fixed.

Git-based and Graph-based combinations fixed

A bug in the discovery logic for Git worktrees prevented using a combination of Git-based and Graph-based filter expressions in the same filter from working correctly.

e.g.

 terragrunt find --filter '...^[HEAD^...HEAD]...'

That bug has been fixed.

Proper exit codes returned from -detailed-exitcode

A bug in the logic for handling retries combined with the OpenTofu/Terraform plan -detailed-exitcode and the Terragrunt --all flag resulted in the wrong exit code being returned when a failed run succeeded on a subsequent retry with a status code related to drift (exit code 2).

That logic has been corrected, and properly follows the rules outlined under the --all flag:

When not using -detailed-exitcode:

  • Terragrunt will return the highest exit code of all runs performed.

When using -detailed-exitcode:

  • If any run has an exit code that is 1, or greater than 2, run --all will return the highest exit code.
  • Otherwise, if any run returns an exit code of 2, run --all will return an exit code of 2.
  • Otherwise, run --all will return an exit code of 0.
OpenTelemetry traces in console mode fixed

A bug in OpenTelemetry trace exporting prevented traces from being exported when in console mode. That bug has been fixed.

Negation logic fixed

A bug in how negation logic was handled in filter expressions prevented successful exclusion of stacks from generation and over excluded units in runs when users only supplied negative filters.

⚙️ Process Improvements

GPG Signing

Release artifacts are now signed using both GPG and Cosign.

To start performing signature validation on assets, in addition to the asset you’re downloading from the GitHub releases page, you’ll want to download some of the following files:

VERSION="v0.XX.X"  # Replace with actual version of Terragrunt you are installing
curl -LO "https://github.com/gruntwork-io/terragrunt/releases/download/${VERSION}/SHA256SUMS"

# For GPG:
curl -LO "https://github.com/gruntwork-io/terragrunt/releases/download/${VERSION}/SHA256SUMS.gpgsig"

# For Cosign:
curl -LO "https://github.com/gruntwork-io/terragrunt/releases/download/${VERSION}/SHA256SUMS.sig"
curl -LO "https://github.com/gruntwork-io/terragrunt/releases/download/${VERSION}/SHA256SUMS.pem"

To verify with GPG:

curl -s https://gruntwork.io/.well-known/pgp-key.txt | gpg --import

gpg --verify SHA256SUMS.gpgsig SHA256SUMS

sha256sum -c SHA256SUMS --ignore-missing

To verify with Cosign:

cosign verify-blob SHA256SUMS \
  --signature SHA256SUMS.sig \
  --certificate SHA256SUMS.pem \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp "github.com/gruntwork-io/terragrunt"

sha256sum -c SHA256SUMS --ignore-missing

Terragrunt installation documentation will be updated soon to recommend this on every installation, the Gruntwork maintained asdf plugin will be updated to do this automatically, and all Gruntwork recommended mechanisms for installing Terragrunt will support this going forward.

Upgrade to Go 1.25.5

The Golang toolchain used to build Terragrunt has been upgraded to v1.25.5.

Package reorganization

All top-level Golang packages in the Terragrunt project have been migrated to either internal or pkg. The distinction between the two indicates maintainer expectations as to whether either are being actively being consumed as libraries by third parties (with internal being impossible to import without vendoring in go modules).

Note that this does not indicate any backwards compatibility guarantee for usage of the Terragrunt as a library. It will remain unstable, and can change at any time.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.97.2...v0.98

v0.97.2

Compare Source

🏎️ Performance Improvements

Partial parse used for get_working_dir()

To assess where Terragrunt is going to run OpenTofu, it needs partially parsed information from the relevant terragrunt.hcl file of the unit running the HCL get_working_dir() function. The function was performing a full parse of the terragrunt.hcl file, which can be slow for users with large HCL configurations.

Given that the parse only requires access to the value of source in the terraform block, a partial parse is now performed by the function, only looking at the contents of the terraform block, improving performance significantly.

🐛 Bug Fixes

False positive parsing errors suppressed

When parsing an include that defined dependencies, the HCL parser used by Terragrunt would emit spurious errors that are internally ignored. Those messages are now suppressed.

Signal propagation for interrupts fixed

A bug in how Terragrunt forwarded signals to processes it spawned (like running tofu) resulted in underlying processes receiving SIGKILL signals rather than the original signal (e.g. SIGINT) sent to the Terragrunt process. That has been fixed.

🧹 Chores

Avoiding contextcheck suppression

While not changing much functionally in Terragrunt, this release did involve quite a lot of changes to Terragrunt internals. The majority of these changes related to better propagation of the Golang [context](https://pkg.go.dev/context) object to better obey Golang best practices. These issues were reported by the contextcheck linter in the codebase, but the findings were suppressed due to the scope of work required to address them.

These changes should make it so that context is propagated correctly more reliably in the codebase, increasing the usefulness of things like OpenTelemetry tracing and reduced resource usage.

Note that some public function signatures have changed in the Terragrunt codebase, which may be a breaking change to users consuming Terragrunt as a library. Given that we do not offer any stability guarantees for usage of Terragrunt as a library, these changes are still to be included in a patch release.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.97.1...v0.97.2

v0.97.1

Compare Source

✨ New Features

All HCL functions instrumented with OpenTelemetry

All Terragrunt HCL functions now emit OpenTelemetry spans when they run, making it easier to understand HCL function usage and performance.

HCL parsing telemetry improved

Additional fidelity has been added to traces emitted during parsing to give insight as to why configuration parsing is being performed, and how.

🐛 Bug Fixes

plan -destroy called correctly for --filter-affected

A bug in the logic for --filter-affected resulted in removed units getting planned/applied instead of being destroyed when users supplied --filter-allow-destroy. That bug has been fixed.

Nested spans in track parents appropriately even when the TRACEPARENT environment variable is used.

A bug in the logic for propagating TRACEPARENT as the ultimate parent of traces started in Terragrunt prevented child traces from properly tracking parent spans. That bug has been fixed.

Reports on runs in worktrees now use relative directories to worktree root

Instead of displaying runs of units in Git worktrees during Git-based filter expression runs with the absolute path of their directories in a temporary directory, they now display with the path to the unit relative to the root of the worktree.

Unnecessary relationship discovery prevented

Discovery of relationships between units has been made opt-in in the discovery process. This will result in no changes to usage of commands like run --all, but will significantly improve the performance of commands like list and stack generate.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.97.0...v0.97.1

v0.97.0

Compare Source

⚒️ Breaking Changes

The --queue-strict-include flag is deprecated

Terragrunt no longer automatically includes dependencies of included units. As such the --queue-strict-include flag is no longer useful in the Terragrunt CLI.

The flag has been deprecated, and no longer does anything. This flag will not be removed before 2.0.

Run report no longer reports --queue-exclude-dir as a reason for exclusion

Run reports no longer report on units excluded from runs as a consequence of the --queue-exclude-dir flag.

The --units-that-include flag is deprecated

The --units-that-include flag is now an alias for the reading= attribute filter, just like the --queue-include-units-reading flag.

Given that the two flags no longer differ in functionality, and that the functionality of the --units-that-include is no longer strictly including units that are included, the flag has been deprecated.

The double-star strict control is complete

The globbing behavior of Terragrunt in CLI flags has been updated to match all paths when ending with a trailing ** .

🧪 Experiments Completed

The filter-flag experiment is completed

The filter-flag experiment is completed, and the --filter flag is now generally available.

You can use filter expressions as a single unified API for controlling the Run Queue, replacing the need to use the following CLI flags:

Legacy —queue flag Equivalent —filter expression
—-queue-include-dir=path —-filter='{./path}'
—-queue-exclude-dir=path —-filter='!{./path}'
--queue-include-units-reading=root.hcl --filter='reading=root.hcl'
--units-that-include=root.hcl --filter='reading=root.hcl'
--queue-include-external-dependencies --filter='{./**}...'
--queue-excludes-file=excludes.txt --filters-file='filters.txt' *
--graph --filter='...{.}'
  • Note that the file used for the --queue-excludes-file does not directly translate to the kind of file you can use for a --filters-file. To learn more, see the documentation.

The table above also explains the aliasing that has been done internally to replace queue flags with their filter equivalents. The aliasing for these queue flags is present purely for backwards compatibility purposes, but they are not going to emit deprecation warnings, and will not be removed before the Terragrunt 1.0 release.

You are heavily encouraged to adopt the new --filter flag for your infrastructure targeting needs as soon as feasible in your workflows. It will offer a significantly more flexible and powerful experience.

To learn more see the Filters feature documentation.

🐛 Bug Fixes

The get_original_terragrunt_dir() function is now supported in terragrunt.stack.hcl files

When authoring explicit stacks, using the get_original_terragrunt_dir() HCL function in terragrunt.stack.hcl files will now return the directory where the terragrunt.stack.hcl file lives, even when the configuration is read from another stack/unit using read_terragrunt_config().

Using Git-based expressions with the --out-dir flag is fixed

When using Git-based expressions using the --filter flag, the relative path of units relative to their respective Git worktree roots is used for determining where the plan file will be saved, rather than a path in the relevant Git worktree.

Color for output fetching is suppressed more reliably

Terragrunt will use tofu output -json / terraform output -json more reliably when users expect a lack of colors (like when colors are suppressed for Terragrunt).

What's Changed

New Contributors

Full Changelog: https://github.com/gruntwork-io/terragrunt/compare/v0.96.1..v.0.97.0

v0.96.1

Compare Source

🧪 Experiments Updated

The --filter-affected flag has more robust determination of the default branch in a Git repository

The --filter-affected flag will now use Git plumbing to interrogate the default branch as considered by the remote repository before falling back to interrogating local configurations for determination of a default branch (remember that you must use the filter-flag experiment to try this out).

# This is checked first
$ git rev-parse --abbrev-ref origin/HEAD

# Followed by this
$ git ls-remote --symref origin HEAD

# Followed with this
$ git config init.defaultBranch

# If none of the above succeed, the default branch is assumed to be `main`.
Git-based filter expressions now warn users when using local state

Usage of --filter Git-based expressions in combination with local state will now emit a warning, recommending usage of remote states (remember that you must use the filter-flag experiment to try this out).

$ terragrunt run --all --filter '[HEAD~1...HEAD]' -- plan
09:30:38.017 WARN   One or more units discovered using Git-based filter expressions (e.g. [HEAD~1...HEAD]) do not have a remote_state configuration. This may result in unexpected outcomes, such as outputs for dependencies returning empty. It is strongly recommended to use remote state when working with Git-based filter expressions.

See the warning at the bottom of Git-based expressions documentation for more information.

OpenTelemetry traces added for filter evaluation

Filter evaluation now emits OpenTelemetry spans and metrics, including filter resolution details, evaluation duration, and filtering scope. This helps teams analyze performance and pinpoint bottlenecks in filtering with large Terragrunt repositories.

filter-otel-traces

🐛 Bug Fixes

Path-based filters targeting external paths fixed

A bug in the parsing of path-based filter expressions in the --filter flag of the filter-flag experiment prevented parsing of path-based filters for external paths (e.g. --filter ../external-dir). This bug has been fixed.

HTTPS Git CAS URLs fixed

A bug in the parsing of source URLs with forced usage of the Git protocol (e.g. git::https://github.com/acme/catalog) prevented using the cas experiment with HTTPS Git URLs with forced usage of the Git protocol. This bug has been fixed.

Regression of support for root terragrunt.hcl fixed

A bug in the processing of --queue-exclude-dir resulted in prefix based matching of non-glob expressions in --queue-exclude-dir values. This broke backwards compatibility for users with a root terragrunt.hcl file instead of a differently named file for the root include (e.g. root.hcl). This bug has been fixed.

Note that you are still advised to migrate away from using a root terragrunt.hcl as soon as possible for your team. We will maintain backwards compatibility until at least 2.0, however.

What's Changed

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

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 *

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 terragrunt to v0.89.4 Update dependency terragrunt to v0.90.0 Oct 10, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 57e7a38 to f43ff08 Compare October 10, 2025 17:06
@renovate renovate bot changed the title Update dependency terragrunt to v0.90.0 Update dependency terragrunt to v0.90.1 Oct 15, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from f43ff08 to 56d62e1 Compare October 15, 2025 15:43
@renovate renovate bot changed the title Update dependency terragrunt to v0.90.1 Update dependency terragrunt to v0.91.0 Oct 15, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 56d62e1 to 1a94a89 Compare October 15, 2025 18:53
@renovate renovate bot changed the title Update dependency terragrunt to v0.91.0 Update dependency terragrunt to v0.91.1 Oct 16, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 1a94a89 to 7f7788a Compare October 16, 2025 22:29
@renovate renovate bot changed the title Update dependency terragrunt to v0.91.1 Update dependency terragrunt to v0.91.2 Oct 20, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from 03e575d to 71ff5ca Compare October 23, 2025 17:39
@renovate renovate bot changed the title Update dependency terragrunt to v0.91.2 Update dependency terragrunt to v0.91.4 Oct 23, 2025
@renovate renovate bot changed the title Update dependency terragrunt to v0.91.4 Update dependency terragrunt to v0.91.5 Oct 24, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from 39f90a1 to 8277b21 Compare October 27, 2025 17:53
@renovate renovate bot changed the title Update dependency terragrunt to v0.91.5 Update dependency terragrunt to v0.92.0 Oct 27, 2025
@renovate renovate bot changed the title Update dependency terragrunt to v0.92.0 Update dependency terragrunt to v0.92.1 Oct 28, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from 36d7f39 to fb973a9 Compare October 31, 2025 20:09
@renovate renovate bot changed the title Update dependency terragrunt to v0.92.1 Update dependency terragrunt to v0.93.0 Oct 31, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from fb973a9 to dc71ac3 Compare November 4, 2025 23:05
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.0 Update dependency terragrunt to v0.93.1 Nov 4, 2025
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.1 Update dependency terragrunt to v0.93.3 Nov 5, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from f832999 to 4b51156 Compare November 11, 2025 02:44
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.3 Update dependency terragrunt to v0.93.5 Nov 11, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 4b51156 to a964cd6 Compare November 12, 2025 01:43
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.5 Update dependency terragrunt to v0.93.6 Nov 12, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from a964cd6 to 85665f4 Compare November 12, 2025 19:51
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.6 Update dependency terragrunt to v0.93.8 Nov 12, 2025
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.12 Update dependency terragrunt to v0.93.13 Dec 5, 2025
@renovate renovate bot changed the title Update dependency terragrunt to v0.93.13 Update dependency terragrunt to v0.94.0 Dec 8, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from c7211a7 to 16fbb45 Compare December 8, 2025 20:10
@renovate renovate bot changed the title Update dependency terragrunt to v0.94.0 Update dependency terragrunt to v0.95.0 Dec 12, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from 27da0e1 to f0b5b8a Compare December 12, 2025 22:48
@renovate renovate bot changed the title Update dependency terragrunt to v0.95.0 Update dependency terragrunt to v0.95.1 Dec 12, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from f0b5b8a to 2c1a360 Compare December 15, 2025 22:02
@renovate renovate bot changed the title Update dependency terragrunt to v0.95.1 Update dependency terragrunt to v0.96.0 Dec 15, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 2c1a360 to b7249ce Compare December 17, 2025 18:12
@renovate renovate bot changed the title Update dependency terragrunt to v0.96.0 Update dependency terragrunt to v0.96.1 Dec 17, 2025
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from b7249ce to f63ba3a Compare January 5, 2026 17:08
@renovate renovate bot changed the title Update dependency terragrunt to v0.96.1 Update dependency terragrunt to v0.97.0 Jan 5, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from f63ba3a to 52fd5c9 Compare January 7, 2026 18:36
@renovate renovate bot changed the title Update dependency terragrunt to v0.97.0 Update dependency terragrunt to v0.97.1 Jan 7, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 52fd5c9 to 940088a Compare January 9, 2026 17:12
@renovate renovate bot changed the title Update dependency terragrunt to v0.97.1 Update dependency terragrunt to v0.97.2 Jan 9, 2026
@renovate renovate bot changed the title Update dependency terragrunt to v0.97.2 Update dependency terragrunt to v0.98.0 Jan 20, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch 2 times, most recently from 0776612 to 734e186 Compare January 27, 2026 01:35
@renovate renovate bot changed the title Update dependency terragrunt to v0.98.0 Update dependency terragrunt to v0.99.0 Jan 27, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 734e186 to 7734925 Compare January 29, 2026 21:36
@renovate renovate bot changed the title Update dependency terragrunt to v0.99.0 Update dependency terragrunt to v0.99.1 Jan 29, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 7734925 to e0ae38b Compare February 13, 2026 17:38
@renovate renovate bot changed the title Update dependency terragrunt to v0.99.1 Update dependency terragrunt to v0.99.2 Feb 13, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from e0ae38b to 50249fd Compare February 18, 2026 22:00
@renovate renovate bot changed the title Update dependency terragrunt to v0.99.2 Update dependency terragrunt to v0.99.3 Feb 18, 2026
@renovate renovate bot force-pushed the renovate/terragrunt-0.x branch from 50249fd to beba120 Compare February 20, 2026 02:00
@renovate renovate bot changed the title Update dependency terragrunt to v0.99.3 Update dependency terragrunt to v0.99.4 Feb 20, 2026
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