We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 26 since January 2026, each linked to its source.
terragruntWhen bootstrapping an Azure `azurerm` backend with Azure AD authentication, enable the `azure-backend` experiment and set `assign_blob_data_role = true` to grant Storage Blob Data Contributor to Terragrunt’s authenticated identity. Set `principal_id` to grant the role to a different identity.
terragrunt --experiment azure-backend backend bootstrapWhen a stack configuration needs multiple units from one block, enable the `block-iteration` experiment and add an `expansion` block with `for_each` or `count`; give each unit a distinct path and address generated elements by key or index.
unit "aurora" {
expansion {
for_each = toset(["web", "api"])
}
source = "../units/app"
path = "aurora/${each.key}"
values = { role = each.key }
}When dependency-filter traversal in an isolated monorepo could reach sibling environments, enable `bounded-discovery` and constrain the graph search to the intended environment. Use `--discovery-boundary` for the command or an inline `(dir)` operand for one filter expression; the directory must exist.
cd <environment-dir>
terragrunt run --all plan --experiment bounded-discovery --filter '...{<unit>}' --discovery-boundary .When catalog results must be read without a terminal or saved for review, enable the `catalog-format` experiment and run `terragrunt catalog --experiment=catalog-format --format=jsonl` for JSON Lines or `--format=md` for Markdown; use `jq` to project or remove JSONL fields and check Markdown’s closing table and count for completeness.
terragrunt catalog --experiment=catalog-format --format=jsonl | jq -c '{kind, title, component_source}'When you need to initialize without resolving dependency outputs, set `TG_EXPERIMENT=optional-dependency-outputs` and run `terragrunt run --no-dependency-outputs -- init`. The flag requires the experiment; without it, the command returns an error.
TG_EXPERIMENT=optional-dependency-outputs terragrunt run --no-dependency-outputs -- initWhen an Azure Storage remote-state configuration uses `azurerm`, enable the `azure-backend` experiment and run `terragrunt --experiment azure-backend run -- plan` to manage backend resources and state blobs. [Release v1.1.2](https://github.com/gruntwork-io/terragrunt/releases/tag/v1.1.2)
terragrunt --experiment azure-backend run -- planWhen using Terragrunt v1.1.2 to fetch an OpenTofu module from an OCI registry, enable the `oci` experiment and set `terraform.source` to an `oci://` URL. Pin it with `tag` or `digest`; omitting both selects `latest`.
terraform {
source = "oci://<registry>/<repository>/<module>?tag=<tag>"
}For a `tfr://` registry module in Terragrunt v1.1.1, enable the `version-attribute` experiment and set `version` to a constraint; Terragrunt resolves the highest published match before downloading. Do not also set `?version=` on that source.
terraform {
source = "tfr://registry.opentofu.org/terraform-aws-modules/vpc/aws"
version = "~> 3.3"
}When generating stacks from a catalog with relative source paths, set `update_source_with_cas = true` on the relevant `unit`, `stack`, or `terraform` block; `terragrunt stack generate` rewrites the path to a CAS reference. To edit fetched CAS content in `.terragrunt-cache`, set `mutable = true` on the applicable block; otherwise CAS materializes content read-only.
terragrunt run --all --no-cas -- planWhen you want to browse catalog components and scaffold one into a repository, run `terragrunt catalog`, select the component, and press `s` to open the interactive form. The form collects values and scaffolds the component into the working directory.
terragrunt catalog