Skip to content

chore(deps): update dependency gruntwork-io/terragrunt to v0.93.12 #10

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

chore(deps): update dependency gruntwork-io/terragrunt to v0.93.12 #10

wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 5, 2023 •
edited
Loading

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor v0.42.4 -> v0.93.12

Release Notes

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

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

v0.91.4

Compare Source

🧪 Experiments Updated

filter-flag updated with reading= support

The --filter flag now supports usage of the reading= attribute to filter on components that read particular shared infrastructure configurations.

e.g.

terragrunt find --filter 'reading=shared.hcl'
terragrunt find --filter 'reading=common/*.hcl' # Globs supported!
terragrunt find --filter 'reading=config/**' # Double-wildcard globs are required filtering on files nested in subdirectories.
terragrunt find --filter 'reading=config/vars.tfvars'

This behavior is similar to that provided by the --queue-include-units-reading flag, with additional support for globs, negation and filter chaining supported in the --filter flag more generally.

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

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

What's Changed

New Contributors

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

v0.91.3

Compare Source

✨ New Features

--reading flag added to the find command

The find command now supports the --reading flag, which allows you to discover the shared configurations read by units and stacks when using the --json format.

$ terragrunt find --reading --json
[
  {
    "type": "unit",
    "path": "aws-account-1",
    "reading": [
      "aws-data.yml"
    ]
  },
  {
    "type": "unit",
    "path": "aws-account-2",
    "reading": [
      "aws-data.yml"
    ]
  },
  {
    "type": "unit",
    "path": "gcp-project-1",
    "reading": [
      "gcp-data.hcl"
    ]
  }
]

You can use this information to drive custom logic in your workflows based on the changes related to particular files.

e.g.

$ terragrunt find --reading --json | jq '[.[] | select(.reading[]? | contains("aws-data.yml"))| .path]'
[
  "aws-account-1",
  "aws-account-2"
]

$ terragrunt find --reading --json | jq '[.[] | select(.reading[]? | contains("gcp-data.hcl"))| .path]'
[
  "gcp-project-1"
]

You can learn more about the --reading flag in the find documentation.

🐛 Bug Fixes

Empty stacks no longer throw errors

Previously, a bug in the logic used for making sure that users didn’t accidentally run on empty stacks resulted in users getting a non-zero exit code when all units in a stack were excluded (e.g. via the exclude block).

That bug has been fixed.

Dependency outputs can now be used in generate blocks

Previously, a bug in the way HCL parsing was done during discovery resulted in errors being thrown for users when dependency outputs were used in generate blocks. That error has since been resolved.

That bug has been fixed.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.91.2...v0.91.3

v0.91.2

Compare Source

🧪 Experiments Introduced

filter-flag introduced

A new experiment named filter-flag has been introduced, allowing for experimental usage of the new --filter flag described in RFC #​4060. The filter-flag experiment is incomplete, and minimal support for the --filter flag has been added exclusively to the find and list commands.

The filter flag allows for sophisticated querying of particular Terragrunt stacks and units in a way that is currently only possible using a combination of —queue- prefixed flags.

Example filter usage might look like the following:

$ terragrunt find --filter './prod/** | name=web'
prod/services/web

[!IMPORTANT]

While the filter-flag experiment is active, you will need to enable the filter-flag experiment for any command that uses the filter-flag. See Controlling Experiment Mode for more details.

e.g.

terragrunt find --experiment filter-flag --filter './prod/** | name=web'

You can learn more about filters, including documentation on the syntax and examples of each type of filter in the dedicated feature documentation for filters.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.91.1...v0.91.2

v0.91.1

Compare Source

🧹 Chores

Updated dependencies

Upgraded multiple Golang dependencies to the latest stable versions:

  • Updated cloud.google.com/go/storage to v1.57.0
  • Updated github.com/aws/aws-sdk-go-v2 to v1.39.2
  • Updated github.com/getsops/sops/v3 to v3.11.0
  • Updated github.com/gofrs/flock to v0.13.0
  • Updated github.com/gruntwork-io/terratest to v0.51.0
  • Updated github.com/hashicorp/go-getter to v1.8.2
  • Updated golang.org/x/mod to v0.29.0
  • Updated golang.org/x/oauth2 to v0.32.0
  • Updated golang.org/x/sys to v0.37.0
  • Updated golang.org/x/term to v0.36.0
  • Updated golang.org/x/text to v0.30.0
  • Updated google.golang.org/api to v0.252.0
  • Updated google.golang.org/grpc to v1.76.0
  • Updated google.golang.org/protobuf to v1.36.10

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.91.0...v0.91.1

v0.91.0

Compare Source

Removal of behavior where inputs are read from dependencies

🛠️ Breaking Changes

Removal of behavior where inputs are read from dependencies

Terragrunt no longer exposes dependency inputs as accessible values.

This change improves performance and simplifies dependency handling by removing a feature that significantly slowed configuration parsing due to a requirement for recursive parsing of dependencies of dependencies for every dependent.

If your configurations currently access dependency inputs like this:

dependency "foo" {
  config_path = "../foo"
}

inputs = {
  my_input = dependency.foo.inputs.an_input_from_foo
}

You’ll need to update them to reference outputs instead:

dependency "foo" {
  config_path = "../foo"
}

inputs = {
  my_input = dependency.foo.outputs.an_output_from_foo
}

Accessing outputs remains the supported and recommended way to share data between modules.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.90.2...v0.91.0

v0.90.2

Compare Source

✨ New Features

Added --terragrunt-no-cache flag for run_cmd

The run_cmd command now supports a new flag, --terragrunt-no-cache, which disables caching of command execution output.

This option is useful when you want to ensure that each command run produces fresh results, especially in dynamic environments or when working with frequently changing external data.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.90.1...v0.90.2

v0.90.1

Compare Source

✨ New Features

hcl fmt now supports --queue flags

The hcl fmt command now supports --queue- prefixed flags (e.g. --queue-exclude-dir).

🐛 Bug Fixes

Discovery in run command discovers hidden directories

When discovering units for the run command, Terragrunt will now search through (most) hidden directories.

It will still avoid performing discovery in the following hidden directories:

  • .git
  • .terraform
  • .terragrunt-cache

To manually force or suppress discovery, use --queue-include-dir and --queue-exclude-dir respectively.

--queue-ignore-errors no longer breaks DAG resolution

A bug in the implementation of --queue-ignore-errors resulted in the flag also preventing the proper resolution of the Directed Acyclic Graph (DAG) when suppressing errors.

This has been fixed.

--tf-path respected through dependencies

A bug in the precedence resolution of the terraform_binary HCL attribute and the --tf-path flag resulted in the default value of terraform_binary taking affect (tofu if both tofu and terraform are installed) when terraform_binary was not specified in dependencies.

This bug has been resolved, and the --tf-path flag will be respected in dependencies as well.

Spurious errors resolved in read_terragrunt_config()

A bug caused the read_terragrunt_config() HCL function to return spurious errors when used in a configuration parsed during the discovery phase of configuration resolution of a run.

This has been fixed.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.90.0...v0.90.1

v0.90.0

Compare Source

Removal of deprecated commands

This is the next step on the road to Terragrunt 1.0, completing the Terragrunt CLI Redesign. Read the CLI Redesign migration guide for guidance on adapting to these breaking changes.

We anticipate no further breaking changes to the CLI prior to the release of Terragrunt 1.0, where the CLI will remain stable without breaking changes until at least Terragrunt 2.0.

For a full list of deprecated features that will be removed prior to the release of Terragrunt 1.0, see the removal schedule.

🛠️ Breaking Changes

Removal of Deprecated Commands

The following deprecated CLI commands have been removed to streamline the command line API ahead of 1.0.

Use the new commands introduced during the CLI redesign that replace them:

  • terragrunt terragrunt-info → terragrunt info print
  • terragrunt hclfmt → terragrunt hcl fmt
  • terragrunt hclvalidate → terragrunt hcl validate
  • terragrunt validate-inputs → terragrunt hcl validate --inputs
  • terragrunt render-json → terragrunt render --json -w
  • terragrunt graph-dependencies → terragrunt dag graph
  • terragrunt output-module-groups → terragrunt find --dag --json

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.89.4...v0.90.0

v0.89.4

Compare Source

🐛 Bug Fixes

Collection of exit code for -detailed-exitcode behavior in run --all

Improved run-all plan -detailed-exitcode aggregation to correctly return 2 when any unit has drift, even if another unit hits a retryable error.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.89.3...v0.89.4

v0.89.3

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.89.2...v0.89.3

v0.89.2

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.89.1...v0.89.2

v0.89.1

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.89.0...v0.89.1

v0.89.0

Compare Source

Several experimental features have been made generally available.

🛠️ Breaking Changes

Runner-pool

Terragrunt now supports the Runner Pool concurrency model, replacing t

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 2ee6dce to 65340be Compare January 5, 2023 11:46
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.5 chore(deps): update dependency gruntwork-io/terragrunt to v0.42.6 Jan 5, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 65340be to 05d4157 Compare January 5, 2023 14:21
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.6 Update dependency gruntwork-io/terragrunt to v0.42.6 Jan 5, 2023
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.42.6 chore(deps): update dependency gruntwork-io/terragrunt to v0.42.6 Jan 5, 2023
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.6 chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 Jan 6, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 05d4157 to a40dace Compare January 6, 2023 12:09
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 - autoclosed Jan 13, 2023
@renovate renovate bot closed this Jan 13, 2023
@renovate renovate bot deleted the renovate/gruntwork-io-terragrunt-0.x branch January 13, 2023 10:17
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 - autoclosed chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 Jan 13, 2023
@renovate renovate bot restored the renovate/gruntwork-io-terragrunt-0.x branch January 13, 2023 14:04
@renovate renovate bot reopened this Jan 13, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a40dace to 2e5ebd3 Compare January 13, 2023 17:41
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.7 chore(deps): update dependency gruntwork-io/terragrunt to v0.42.8 Jan 13, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2e5ebd3 to d5edc95 Compare January 19, 2023 16:42
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.42.8 chore(deps): update dependency gruntwork-io/terragrunt to v0.43.0 Jan 19, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from d5edc95 to 8e51b6c Compare January 31, 2023 21:41
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.43.0 chore(deps): update dependency gruntwork-io/terragrunt to v0.43.1 Jan 31, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 8e51b6c to 96db405 Compare February 2, 2023 23:07
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.43.1 chore(deps): update dependency gruntwork-io/terragrunt to v0.43.2 Feb 2, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 96db405 to ed38379 Compare February 22, 2023 20:20
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.43.2 chore(deps): update dependency gruntwork-io/terragrunt to v0.43.3 Feb 22, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ed38379 to a322627 Compare February 22, 2023 22:49
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.43.3 chore(deps): update dependency gruntwork-io/terragrunt to v0.44.0 Feb 22, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a322627 to fe07894 Compare February 28, 2023 17:52
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.44.0 chore(deps): update dependency gruntwork-io/terragrunt to v0.44.1 Feb 28, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from fe07894 to 8bcf59d Compare March 1, 2023 23:24
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.44.1 chore(deps): update dependency gruntwork-io/terragrunt to v0.44.2 Mar 1, 2023
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 8bcf59d to 239df31 Compare March 2, 2023 23:20
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.88.0 chore(deps): update dependency gruntwork-io/terragrunt to v0.88.1 Oct 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from bb05af7 to c441dec Compare October 6, 2025 20:02
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.88.1 chore(deps): update dependency gruntwork-io/terragrunt to v0.89.0 Oct 6, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c441dec to 00317f4 Compare October 8, 2025 23:00
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.89.0 chore(deps): update dependency gruntwork-io/terragrunt to v0.89.3 Oct 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 00317f4 to 1391726 Compare October 10, 2025 04:06
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.89.3 chore(deps): update dependency gruntwork-io/terragrunt to v0.89.4 Oct 10, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 1391726 to f43830a Compare October 11, 2025 03:47
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.89.4 chore(deps): update dependency gruntwork-io/terragrunt to v0.90.0 Oct 11, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from f43830a to 5405eb3 Compare October 16, 2025 23:54
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.90.0 chore(deps): 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 5405eb3 to a0f013b Compare October 20, 2025 19:59
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.91.1 chore(deps): 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 from a0f013b to 32d6379 Compare October 25, 2025 16:06
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.91.2 chore(deps): update dependency gruntwork-io/terragrunt to v0.91.5 Oct 25, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 32d6379 to 31b36d0 Compare November 1, 2025 23:34
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.91.5 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.0 Nov 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 31b36d0 to 32ff610 Compare November 8, 2025 19:47
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.0 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.3 Nov 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 32ff610 to c9db20c Compare November 16, 2025 00:11
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.3 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.8 Nov 16, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c9db20c to 90198d4 Compare November 19, 2025 23:38
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.8 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.9 Nov 19, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 90198d4 to d57cff0 Compare November 22, 2025 03:57
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.9 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.10 Nov 22, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from d57cff0 to 832f704 Compare November 25, 2025 04:14
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.10 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.11 Nov 25, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 832f704 to 3d71d88 Compare December 1, 2025 23:27
@renovate renovate bot changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.93.11 chore(deps): update dependency gruntwork-io/terragrunt to v0.93.12 Dec 1, 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.

1 participant