terraform-style

To enforce consistent Terraform HCL code style for shared modules, standardize your resource organization, provider configuration, and code formatting rules. This ensures infrastructure as code maintainability and readability across your team.

You format and validate Terraform infrastructure as code automatically by running tofu fmt, terragrunt hcl fmt, and tofu validate. This sequence checks code layout, enforces formatting rules, and validates your configuration.

Yes, this Terraform formatting approach works with Terragrunt and OpenTofu. It explicitly requires terragrunt hcl fmt, tofu fmt, and tofu validate as dependencies to enforce coding conventions and standardize infrastructure as code.

The best way to organize resources in Terraform shared modules is grouping them under clear section headers for better readability. Standardizing code layout and provider configuration ensures consistent coding conventions.

You need tofu fmt and terragrunt hcl fmt for Terraform code style because they standardize code layout and enforce formatting rules. Using these tools ensures proper version pinning and consistent configuration management.

You should standardize Terraform provider configuration and version pinning when developing large Terraform-based infrastructure for shared modules. This ensures code quality, maintainability, and consistent infrastructure as code deployment.