terraform-style-guide

Terraform modules following HashiCorp style conventions use a predictable file organization, separating providers, data sources, resources, variables, locals, and outputs into distinct files like main.tf and variables.tf to improve readability and collaboration.

Secure Terraform HCL configurations enforce the principle of least privilege, avoid hardcoded secrets, mark sensitive outputs appropriately, and implement variable validation to prevent insecure deployments.

Consistent Terraform code relies on enforcing idiomatic naming conventions, indentation, and block ordering that match common infrastructure as code best practices, reducing the risk of inconsistent and hard-to-review configurations.

The style guide applies when writing, reviewing, or generating Terraform HCL for modules, ensuring any new deployment or refactored infrastructure matches HashiCorp's formatting rules and security best practices.

Terraform code requires variable descriptions and validation to enforce security best practices and ensure correct inputs, producing predictable, reliable infrastructure as code deployments that align with HashiCorp style conventions.

The best way to organize Terraform files is using a standard layout like terraform.tf, providers.tf, main.tf, variables.tf, and outputs.tf, which enforces predictable module structure and enhances team collaboration.