Skip to content

Commit d7d10bc

Browse files
denis256yhakbar
andauthored
Update docs-starlight/src/content/docs/01-getting-started/04-terminology.md
Co-authored-by: Yousif Akbar <11247449+yhakbar@users.noreply.github.com>
1 parent a4bad00 commit d7d10bc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs-starlight/src/content/docs/01-getting-started/04-terminology.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Note that runs abstract away a lot of the complexity that comes from working wit
140140

141141
The way in which these complexities are abstracted is via Terragrunt configuration files (`terragrunt.hcl`), which can be used to define how Terragrunt should forward commands to OpenTofu/Terraform.
142142

143-
Note: As of v0.88.0, Terragrunt no longer forwards unknown commands to OpenTofu/Terraform by default. Use the explicit `run` command (e.g., `terragrunt run -- workspace ls`) or supported shortcuts.
143+
There is an explicit list of [supported shortcuts](https://terragrunt.gruntwork.io/docs/reference/cli/commands/opentofu-shortcuts/) that Terragrunt will forward to OpenTofu/Terraform by default. For all other commands that need to be forwarded to OpenTofu/Terraform, use the `run` command (e.g., `terragrunt run -- workspace ls`).
144144

145145
In the simplest case, a run in a unit with an empty `terragrunt.hcl` file will be equivalent to running OpenTofu/Terraform directly in the unit directory (with some small additional features like automatic initialization and logging adjustments).
146146

0 commit comments

Comments
 (0)