Skip to content

Update dependency gruntwork-io/terragrunt to v0.77.22 #390

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

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

Update dependency gruntwork-io/terragrunt to v0.77.22 #390

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor 0.72.1 -> 0.77.22

Release Notes

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

v0.77.22

Compare Source

🧪 Experiments Completed

The cli-redesign experiment is now complete

The cli-redesign experiment is now complete.

If you were previously using the flag --experiment cli-redesign to opt in to experimental functionality, you no longer have to do so. Note that if you are, you will simply get a warning that it is no longer necessary.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.21...v0.77.22

v0.77.21

Compare Source

✨ New Features

Introduction of hcl commands

As part of the CLI Redesign experiment, the hcl commands has been introduced.

The hcl commands allow users to directly interact with HCL content independent of the underlying functionality they support.

The functionality of the hcl commands replace existing functionality that is soon to be deprecated:

  • hclfmt --> hcl fmt
  • hclvalidate --> hcl validate
  • validate-inputs --> hcl validate --inputs
  • validate-inputs --strict-validate --> hcl validate --inputs --strict

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.77.20...v0.77.21

v0.77.20

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.19...v0.77.20

v0.77.19

Compare Source

✨ New Features

OpenTelemetry traces are now integrated into find and list commands

find telemetry:
image

list telemetry:
image

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.18...v0.77.19

v0.77.18

Compare Source

✨ New Features

Support for HCL formatting with the render command

As part of the CLI Redesign experiment, the render command now supports HCL formatting for rendered configurations, which is the default output format.

Using the render command with HCL formatting allows users to get a quick, minimal evaluation of Terragrunt unit configurations with as much pre-processing done as possible.

For example, the following terragrunt.hcl file:

### terragrunt.hcl

locals {
  aws_region = "us-east-1"
}

inputs = {
  aws_region = local.aws_region
}

Renders to the following HCL:

$ terragrunt render
locals {
  aws_region = "us-east-1"
}
inputs = {
  aws_region = "us-east-1"
}

Using the render command with HCL formatting offers a way to resolve complex HCL function evaluation, include merging or string interpolation, etc. to achieve equivalent Terragrunt HCL configurations that are easier to reason about.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.17...v0.77.18

v0.77.17

Compare Source

✨ New Features

Introduction of the render command

As part of the CLI Redesign experiment, the render command has been introduced.

The render command allows users to easily render Terragrunt unit configurations with reduced complexity, making it easier to understand configurations at a glance.

For example, the following terragrunt.hcl file:

### terragrunt.hcl

locals {
  aws_region = "us-east-1"
}

inputs = {
  aws_region = local.aws_region
}

Renders to the following JSON:

$ terragrunt render --format json
{
  "locals": { "aws_region": "us-east-1" },
  "inputs": { "aws_region": "us-east-1" }
  // NOTE: other attributes are omitted for brevity
}

The introduction of the render command is part of the eventual deprecation of the existing render-json command, which will be deprecated by the end of the CLI Redesign. The render command is a higher level command, that offers the ability to write to stdout, in addition to writing to files, and will support HCL configurations in addition to JSON (coming soon).

To learn more about the render command, read the official documentation here.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.16...v0.77.17

v0.77.16

Compare Source

✨ New Features

Introduction of the backend migrate command

As part of the CLI Redesign experiment, the backend migrate command has been introduced.

The backend migrate command allows you to simply migrate state between different units (or renames of units) without manually running OpenTofu/Terraform state migration commands.

To learn more about the backend migrate command, read the official docs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.15...v0.77.16

v0.77.15

Compare Source

✨ New Features

Introduction of the dag graph command

As part of the CLI Redesign experiment, the dag graph command has been introduced.

dag

dag-help

dag-graph-help

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.14...v0.77.15

v0.77.14

Compare Source

✨ New Features

Support for --exclude and --queue-construct-as in find and list

The find and list commands have been updated to leverage new capabilities involving greater understanding of the Terragrunt run queue.

Users can now leverage the --queue-construct-as (or just --as) flag in the find and list commands to discover configurations as if a particular Terragrunt command was being run (e.g. plan, destroy).

For example:

$ terragrunt find --queue-construct-as=plan
stacks/live/dev
stacks/live/prod
units/live/dev/vpc
units/live/prod/vpc
units/live/dev/db
units/live/prod/db
units/live/dev/ec2
units/live/prod/ec2
$ terragrunt find --as=destroy
stacks/live/dev
stacks/live/prod
units/live/dev/ec2
units/live/prod/ec2
units/live/dev/db
units/live/prod/db
units/live/dev/vpc
units/live/prod/vpc

The find and list commands will now construct the Terragrunt run queue as if a particular command was being run, potentially altering the position of elements in the run queue, based on their dependencies (dependencies before dependents for plans, applies, etc. and dependents before dependencies for destroys).

In addition, users can leverage the --exclude flag on the find command to get information on the exclude block included in results. The exclude block is also factored in to discovery results when the --queue-construct-as flag is passed, allowing users to dry-run behavior of the exclude block before performing any Terragrunt runs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.13...v0.77.14

v0.77.13

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.12...v0.77.13

v0.77.12

Compare Source

✨ New Features

Introduced no_validation attribute for stack and unit, allowing users to bypass Terragrunt's validation checks when deploying infrastructure. This is particularly useful in scenarios where you need to deploy infrastructure that doesn't strictly adhere to Terragrunt's validation rules, such as during emergency deployments or when working with legacy infrastructure patterns.

What's Changed

RFC: https://github.com/gruntwork-io/terragrunt/issues/3313

Full Changelog: gruntwork-io/terragrunt@v0.77.11...v0.77.12

v0.77.11

Compare Source

✨ New Features

Introduction of the info print command

As part of the CLI Redesign experiment, the info print command has been introduced.

help

out

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.10...v0.77.11

v0.77.10

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.9...v0.77.10

v0.77.9

Compare Source

🐛 Bug fixes

Fetching Outputs from Nested Stacks

Resolved an issue that prevented the correct retrieval of outputs from nested stacks.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.8...v0.77.9

v0.77.8

Compare Source

📖 Documentation Updates

A new performance guide has been added to Terragrunt documentation to offer guidance on how performance can be improved when using Terragrunt or contributing to the Terragrunt codebase.

This documentation will evolve over time, as more optional optimizations become available, or are no longer necessary, as they become default behavior.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.7...v0.77.8

v0.77.7

Compare Source

✨ New Features

Users can now configure a custom default template for scaffold and catalog commands in their catalog configuration blocks like so:

catalog {
  default_template = "[email protected]/acme/example.git//path/to/template"
}

For more information, read the documentation in the catalog feature.

Special thanks to @​tgeijg for contributing this feature!

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.77.6...v0.77.7

v0.77.6

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.5...v0.77.6

v0.77.5

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.4...v0.77.5

v0.77.4

Compare Source

🐛 Bug fixes

Newlines reduced in Error Logging for Configuration Errors

Logging for configuration errors has been compacted to reduce noise, and make errors easier to read.


### Before
14:09:25.892 ERROR  Error: Error in function call

14:09:25.892 ERROR    on terragrunt.hcl line 3, in locals:

14:09:25.892 ERROR     3:       requires_auth = run_cmd("exit", "1") // intentional error

14:09:25.892 ERROR

14:09:25.892 ERROR  Call to function "run_cmd" failed: Failed to execute "exit 1" in .

exec: "exit": executable file not found in $PATH.


### After
15:19:50.937 ERROR  Error: Error in function call
15:19:50.937 ERROR    on terragrunt.hcl line 3, in locals:
15:19:50.937 ERROR  Error: Error in function call
15:19:50.937 ERROR    on terragrunt.hcl line 3, in locals:
15:19:50.937 ERROR     3:       requires_auth = run_cmd("exit", "1") // intentional error
15:19:50.937 ERROR     3:       fail   = run_cmd("exit", "1") // intentional error
15:19:50.937 ERROR  Call to function "run_cmd" failed: Failed to execute "exit 1" in .
15:19:50.937 ERROR  exec: "exit": executable file not found in $PATH.
Improved Cycle Detection Logic for stack generate

On the default filesystem for macOS, path length was likely to result in an error before internal cycle detection logic, so cycle detection was updated to leverage a maximum path length of 1024 characters as an earlier exit for all operating systems.

Excessive warning for bootstrap requirement resolved

Internal logic for determination that backends required bootstrapping was adjusted to no longer leverage the value of the OpenTofu state file.

While cheaper than making a network request to assess the current state of backend resources, it also resulted in false negatives, which triggered excessive backend bootstrap warnings.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.3...v0.77.4

v0.77.3

Compare Source

💪🏽 Enhancements

Error Handling for Discovery

The find and list commands now leverage improved error handling when discovering configurations throughout Terragrunt projects.

When configurations require authentication due to usage of functionality like get_aws_account_id(), have errors in their configurations or cycles between dependencies, the commands will do their best to return valid results, and warn the user that the results are incomplete due to suppressed errors or cut cycles.

This should allow for usage of the find and list commands in more real-world use-cases, which frequently require this kind of error handling.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.2...v0.77.3

v0.77.2

Compare Source

✨ New Features

The backend configuration block now supports assume_role_with_web_identity for configuring the backend block of the OpenTofu/Terraform terraform block.

This allows users separately authenticating to backends with a different role to leverage role assumption with OIDC.

For more information, see the backend docs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.1...v0.77.2

v0.77.1

Compare Source

✨ New Features

  • Improved error handling by adding a test check for non-existent stack and unit paths, ensuring clearer messages when expected files are missing.
  • Added support for reading stack and values files read_terragrunt_config() now handles both formats.

What's Changed

Validation demo:

stack-validation-v2

Read config demo:

read_terragrunt_config-v2

Stacks RFC: https://github.com/gruntwork-io/terragrunt/issues/3313

Full Changelog: gruntwork-io/terragrunt@v0.77.0...v0.77.1

v0.77.0

Compare Source

🛠️ Breaking Changes

Best Effort Parsing

Exported functions like ParseConfig and ParseConfigString now perform best effort parsing instead of early returns. Consumers of Terragrunt as a library should be aware of this change, as it can result in partially parsed configurations being returned instead of nil when errors are encountered during parsing. As a consumer of these functions, you are responsible for checking the errors being returned, and handling the returned configuration value accordingly.

These changes are being introduced to support greater parsing flexibility for usage in the find and list command, which will be able to handle partial parse failures while still returning valuable information, along with the Terragrunt LSP, which needs the same adjustments to parsing.

Struct Field Alignment

The fieldalignment govet lint has been introduced to the codebase, and all structs that had less efficient struct field alignment have been updated to minimize their memory footprint. If you are consuming Terragrunt as a library, you may have to make changes to how you are leveraging exported structs from Terragrunt.

The simplest way to avoid any breakage related to this change is to avoid usage of unkeyed composite literals.

### before
type Foo struct {
  BoolField bool
  IntField int
}

f := Foo{false, 30}
### after
type Foo struct {
  IntField int
  BoolField bool
}

### Avoid unkeyed struct literals
f := Foo{BoolField: false, IntField: 30}

### Or rearrange the values of your unkeyed struct literal
f := Foo{30, false}
Telemetry Environment Variable Name Changes

The following environment variables now have new aliases:

  • TERRAGRUNT_TELEMETRY_TRACE_EXPORTER --> TG_TELEMETRY_TRACE_EXPORTER
  • TERRAGRUNT_TELEMETRY_TRACE_EXPORTER_HTTP_ENDPOINT --> TG_TELEMETRY_TRACE_EXPORTER_HTTP_ENDPOINT
  • TERRAGRUNT_TELEMETRY_TRACE_EXPORTER_INSECURE_ENDPOINT --> TG_TELEMETRY_TRACE_EXPORTER_INSECURE_ENDPOINT
  • TERRAGRUNT_TELEMETRY_METRIC_EXPORTER --> TG_TELEMETRY_METRIC_EXPORTER
  • TERRAGRUNT_TELEMETRY_METRIC_EXPORTER_INSECURE_ENDPOINT --> TG_TELEMETRY_METRIC_EXPORTER_INSECURE_ENDPOINT

These environment variables have been renamed to align more closely with the rest of the changes in the CLI Redesign.

Note that the TRACEPARENT environment variable has not changed. This environment variable is semi-standard in the OpenTelemetry space, so we've preserved it.

This is not a breaking change with this release, but will be in the future. As with all the environment variable renames that have taken place during the CLI Redesign, both the legacy environment variable and the new environment variable will be supported to give users time to make requisite adjustments. If you would like to opt in to stricter behavior that requires usage of the new environment variables, leverage the terragrunt-prefix-env-vars strict control.

🐛 Inadvertent elevated permissions required for backend management

The changes made to refactor logic for backend management to introduce backend bootstrap inadvertently introduced an expansion in the required AWS IAM permissions used to bootstrap backend resources.

To avoid requiring any permissions adjustments, upgrade to at least v0.77.4, where the logic has been refactored further, and the required permissions have been restored to what they were before.

✨ New Features

Introduction of backend bootstrap and backend delete

This release introduces two new commands named backend bootstrap and backend delete.

These commands allow for manual control over the process by which Terragrunt can manage backend state resources on behalf of users.

backend bootstrap

The backend bootstrap command allows users to explicitly bootstrap resources like S3 buckets, GCS buckets, DynamoDB tables, etc. used to manage state for OpenTofu/Terraform.

It is accompanied by a flag (--backend-bootstrap) which explicitly enables this behavior by default before performing any operation that might require backend resources (like the run command).

The introduction of this command is part of the future deprecation of provisioning backend resources by default when using Terragrunt. You can learn more about this in the CLI Redesign.

backend delete

The backend delete command allows users to delete state resources relevant to one or more units in remote state.

Terragrunt performs two safety checks to mitigate the risk of accidentally removing the wrong backend state resource:

  1. By default, Terragrunt will refuse to remove any backend state file if versioning is not enabled for the backend S3 bucket or GCS bucket. To explicitly ignore this safety check, users must provide the --force flag.
  2. By default, Terragrunt will prompt users to confirm their decision to remove a given backend state file. To explicitly ignore this safety check, users must provide the --non-interactive flag.

The introduction of this command is part of a larger effort to provide users greater control over the full lifecycle of backend state resources by Terragrunt. You can learn more about this in the CLI Redesign.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.8...v0.77.0

v0.76.8

Compare Source

✨ New Features

OpenTofu file extension detection

OpenTofu-specific file extensions (*.tofu and *.tofu.json) are detected by default, just like generic *.tf, *.tf.json files, which are used by both OpenTofu and Terraform.

This ensures that future incompatibility between OpenTofu and Terraform which specifically requires usage of the *.tofu file extension will be supported without additional effort.

Thank you to @​wazy for contributing this new feature.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.76.7...v0.76.8

v0.76.7

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.6...v0.76.7

v0.76.6

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.5...v0.76.6

v0.76.5

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.4...v0.76.5

v0.76.4

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.3...v0.76.4

v0.76.3

Compare Source

🛠️ Breaking Changes

find --sort=dag changed to find --dag

The experimental find command no longer has a --sort flag. Instead the ability to sort configurations according to their position in the DAG has been replaced with the dedicated --dag flag, which puts the command in "DAG Mode". These changes have been done to allow for closer parity in the behavior of find and list.

### Before
terragrunt find --sort=dag

### After
terragrunt find --dag

✨ New Features

Introduction of the list command

As part of the CLI Redesign experiment, the list command has been introduced. As with other new features, usage requires enabling the CLI Redesign experiment.

The list command helps you discover and display Terragrunt configurations in your codebase. It provides various output formats and options to help you understand the structure and dependencies of your Terragrunt configurations.

The list command is very similar to the find command. It uses the same backend logic for configuration discovery. It also supports very similar flags and configuration options.

Generally, the list command is optimized for displaying configurations in a format that is easy for a human to read and understand, so there are more configuration options, and the output is more verbose. Output from the list command can vary significantly depending on the flags used, and the output structure is more variable than that of the find command.

Use the list command when you want to visualize your Terragrunt configurations in a human-readable format. Use the find command when you want to programmatically search for configurations in your codebase.

Usage

By default, the list command will display all discovered configurations with some spacing to display as many as it can on each line.

list

When the size of the output exceeds the width of the terminal, entries will be broken into multiple lines.

list-narrow

Users can additionally request that the --long format is used, which breaks the results over individual lines for each discovered configuration.

list-long

Like with the find command, users can optionally request that dependencies be displayed.

list-long-dependencies

The final format that the list command supports is the tree format:

list-tree

Like with the find command, the list command supports the --dag flag which sorts and groups results according to their relative positions in the Directed Acyclic Graph (DAG).

list-tree-dag

For more information read the documentation in list.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.2...v0.76.3

v0.76.2

Compare Source

✨ New Features

Added --no-stack-generate support in stack run and stack output, allowing users to disable automatic stack regeneration before executing commands. This provides greater control over stack operations by allowing commands to use the existing .terragrunt-stack directory, improving efficiency and avoiding unnecessary updates.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.1...v0.76.2

v0.76.1

Compare Source

✨ New Features

Introduced no_dot_terragrunt_stack support in stack and unit, allowing users to opt out of generating .terragrunt-stack directories. This enables seamless adoption of terragrunt.stack.hcl without requiring state migration for existing infrastructure.

Demo:
no_dot_terragrunt_stack_example_release_example

Stacks RFC: https://github.com/gruntwork-io/terragrunt/issues/3313

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.76.0...v0.76.1

v0.76.0

Compare Source

✨ New Features / 🛠️ Breaking Changes

Catalog/Scaffold no longer requires --root-file-name root.hcl

✨ The catalog and scaffold commands will now attempt to discover a parent root.hcl file by default and use it as the default root Terragrunt configuration when present to help users adopt the changes in migrating-from-root-terragrunt-hcl.

Users that have switched over to use root.hcl as the root of their Terragrunt configurations instead of terragrunt.hcl will no longer need to explicitly pass --root-file-name root.hcl or use the root-terragrunt-hcl strict control to automatically discover the root of their Terragrunt configurations when using catalog or scaffold.

🛠️ Note that this is technically a breaking change to the way that catalog and scaffold work. With this change, users that have both a root.hcl file and a terragrunt.hcl file at the root of their repositories will have the root.hcl file used instead of the terragrunt.hcl file for the catalog and scaffold commands.

If you are not yet ready to rename the terragrunt.hcl file at the root of your repository, use the --root-file-name flag to explicitly provide terragrunt.hcl as the name of the Terragrunt configuration at the root of your Terragrunt

Configuration

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

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

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

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

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

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

@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.2 Update dependency gruntwork-io/terragrunt to v0.72.3 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 052b08f to 2cfcb89 Compare January 21, 2025 21:54
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.3 Update dependency gruntwork-io/terragrunt to v0.72.4 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2cfcb89 to 5bb757d Compare January 23, 2025 22:01
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.4 Update dependency gruntwork-io/terragrunt to v0.72.5 Jan 27, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 5bb757d to 625f376 Compare January 27, 2025 16:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.5 Update dependency gruntwork-io/terragrunt to v0.72.6 Feb 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 625f376 to 6c331c6 Compare February 1, 2025 20:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.6 Update dependency gruntwork-io/terragrunt to v0.72.8 Feb 7, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 6c331c6 to 5230acc Compare February 7, 2025 17:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.8 Update dependency gruntwork-io/terragrunt to v0.72.9 Feb 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 04b1742 to dcba77e Compare February 11, 2025 01:00
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.9 Update dependency gruntwork-io/terragrunt to v0.73.0 Feb 11, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.0 Update dependency gruntwork-io/terragrunt to v0.73.1 Feb 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from dcba77e to 9a071c3 Compare February 12, 2025 14:38
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.1 Update dependency gruntwork-io/terragrunt to v0.73.2 Feb 13, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 9a071c3 to f424dcb Compare February 13, 2025 23:22
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.2 Update dependency gruntwork-io/terragrunt to v0.73.4 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from dbb25b5 to a345a96 Compare February 14, 2025 22:02
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.4 Update dependency gruntwork-io/terragrunt to v0.73.5 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a345a96 to ab34048 Compare February 15, 2025 21:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.5 Update dependency gruntwork-io/terragrunt to v0.73.6 Feb 15, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.6 Update dependency gruntwork-io/terragrunt to v0.73.7 Feb 18, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ab34048 to 32389b7 Compare February 18, 2025 19:40
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.7 Update dependency gruntwork-io/terragrunt to v0.73.8 Feb 20, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 32389b7 to 7478dc6 Compare February 20, 2025 16:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.8 Update dependency gruntwork-io/terragrunt to v0.73.9 Feb 21, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 7478dc6 to ee16f34 Compare February 21, 2025 13:49
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.3 Update dependency gruntwork-io/terragrunt to v0.77.5 Mar 31, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a2ee217 to 72b1729 Compare April 1, 2025 22:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.5 Update dependency gruntwork-io/terragrunt to v0.77.6 Apr 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 72b1729 to 240ef4b Compare April 3, 2025 14:14
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.6 Update dependency gruntwork-io/terragrunt to v0.77.7 Apr 3, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 240ef4b to 57708c1 Compare April 7, 2025 19:32
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.7 Update dependency gruntwork-io/terragrunt to v0.77.9 Apr 7, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 57708c1 to 4d160be Compare April 8, 2025 22:42
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.9 Update dependency gruntwork-io/terragrunt to v0.77.10 Apr 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 4d160be to 773f5f9 Compare April 9, 2025 16:14
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.10 Update dependency gruntwork-io/terragrunt to v0.77.11 Apr 9, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 773f5f9 to b48e1e5 Compare April 10, 2025 23:44
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.11 Update dependency gruntwork-io/terragrunt to v0.77.12 Apr 10, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from b48e1e5 to 3411b6f Compare April 11, 2025 19:55
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.12 Update dependency gruntwork-io/terragrunt to v0.77.14 Apr 11, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 3411b6f to 9d71cae Compare April 14, 2025 18:39
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.14 Update dependency gruntwork-io/terragrunt to v0.77.15 Apr 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 9d71cae to c9df388 Compare April 14, 2025 22:41
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.15 Update dependency gruntwork-io/terragrunt to v0.77.17 Apr 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c9df388 to 9b7b34a Compare April 17, 2025 16:12
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.17 Update dependency gruntwork-io/terragrunt to v0.77.18 Apr 17, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 9b7b34a to 8b94c2b Compare April 17, 2025 19:21
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.18 Update dependency gruntwork-io/terragrunt to v0.77.19 Apr 17, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 8b94c2b to b358005 Compare April 18, 2025 19:25
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.19 Update dependency gruntwork-io/terragrunt to v0.77.20 Apr 18, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from b358005 to ccdef91 Compare April 21, 2025 15:47
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.20 Update dependency gruntwork-io/terragrunt to v0.77.21 Apr 21, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ccdef91 to b89b69f Compare April 21, 2025 18:58
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.77.21 Update dependency gruntwork-io/terragrunt to v0.77.22 Apr 21, 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