How can you format Terraform HCL code according to standard Terraform style convention?

How can you format Terraform HCL code according to standard Terraform style convention?

• A. Run the terraform fmt command during the code linting phase of your CI/CD process
• B. Designate one person in each team to review and format everyone's code
• C. Manually apply two spaces indentation and align equal sign '=' characters in every Terraform file (*.tf)
• D. Write a shell script to transform Terraform files using tools such as AWK, Python, and sed

Answer: (A)

The main idea is to use Terraform’s built-in formatter, terraform fmt, to enforce the standard HCL style automatically. Running terraform fmt formats all Terraform configuration files to the canonical style used by Terraform, handling indentation, spacing around the equals sign, and other formatting details consistently across the entire project. This makes the codebase look uniform no matter who wrote a file, which is exactly what teams need to avoid formatting debates and drift. Why this approach works best is that it relies on an official tool designed for this purpose, so the formatting rules are the ones Terraform expects. It’s easy to integrate into a CI/CD pipeline during the linting phase, ensuring every commit or merge request meets the standard automatically. It can also be run locally or as a pre-commit hook, so developers always work with correctly formatted code from the start. Other approaches, like relying on a single person to format everything or building custom scripts to adjust indentation or alignment, are error-prone and hard to maintain. They can miss edge cases or drift again over time, whereas terraform fmt provides a consistent, repeatable formatting process that aligns with Terraform’s own recommendations.

The main idea is to use Terraform’s built-in formatter, terraform fmt, to enforce the standard HCL style automatically. Running terraform fmt formats all Terraform configuration files to the canonical style used by Terraform, handling indentation, spacing around the equals sign, and other formatting details consistently across the entire project. This makes the codebase look uniform no matter who wrote a file, which is exactly what teams need to avoid formatting debates and drift.

Why this approach works best is that it relies on an official tool designed for this purpose, so the formatting rules are the ones Terraform expects. It’s easy to integrate into a CI/CD pipeline during the linting phase, ensuring every commit or merge request meets the standard automatically. It can also be run locally or as a pre-commit hook, so developers always work with correctly formatted code from the start.

Other approaches, like relying on a single person to format everything or building custom scripts to adjust indentation or alignment, are error-prone and hard to maintain. They can miss edge cases or drift again over time, whereas terraform fmt provides a consistent, repeatable formatting process that aligns with Terraform’s own recommendations.