Native OpenTofu features (Run Observability, concise output, CPU profiling) for Terragrunt stacks using OpenTofu
The native OpenTofu vendor brings OpenTofu-only features: Run Observability, concise output (-concise), CPU profiling, and version-aware feature gating. The migration guide says Terragrunt stacks are excluded, so Terragrunt stacks running OpenTofu (terragrunt { tool = "OPEN_TOFU" }) can’t use any of them.
For us that leaves out most of our account. We’re moving about 160 Terraform-vendor stacks to native OpenTofu, but about 1,150 of our stacks are Terragrunt stacks running OpenTofu, and they account for most of our runs.
Request: support the native OpenTofu features on Terragrunt stacks when tool = OPEN_TOFU. Either of these would work for us:
New options in the Terragrunt vendor config (for example
terragrunt { tool = "OPEN_TOFU", opentofu { logging { concise = true } } }), orA way for the native OpenTofu vendor to run through Terragrunt.
What we’d need to roll it out:
An opt-in per stack, in the UI, the API and the Terraform provider (
spacelift_stack), with no state or vendor migration if possible.The same policy input as native OpenTofu stacks (
input.opentofu), so policies don’t need a separate code path for Terragrunt.Bulk enablement, like the “Migrate stacks to native vendors” widget, since this affects over a thousand stacks.
- Workaround
Log in to comment and vote
No comments yet
Be the first to share your thoughts.