forge-lang-terragrunt

Use centralized Terragrunt configurations to DRY Terraform setups across multiple environments. This approach prevents duplication, reduces manual boilerplate, and ensures consistent structure while minimizing configuration drift.

The safest Terragrunt apply workflow enforces a plan-before-apply discipline. You must run terragrunt validate and terragrunt plan first, ensuring explicit user confirmation is required before any infrastructure changes are applied.

You can use the terragrunt apply --auto-approve flag to skip manual confirmation. However, the default safe guardrails enforce user validation and planning steps before applying changes to prevent unintended infrastructure modifications.

Yes, the Terragrunt workflow enforces hclfmt checks during the deployment process. Formatting validation runs alongside the standard validate, plan, and apply stages to ensure configuration hygiene before changes are applied.

Yes, you need both Terragrunt and Terraform tooling installed. The workflow wraps standard Terraform configurations with safe, DRY practices, relying on the underlying Terraform tooling to operate and execute deployments.