Terraform IaC Conventions

terraformiacinfrastructuredevops

Conventions for writing, organizing and maintaining Terraform configurations

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

Organize resources into modules; never put all resources in a single main.tf file. Use a standard file layout per module: main.tf, variables.tf, outputs.tf, versions.tf. Always pin provider versions in versions.tf using ~> constraints, not latest. Store Terraform state in a remote backend (S3 + DynamoDB lock) for team environments. Never commit terraform.tfstate or .tfvars files containing secrets to version control. Use terraform fmt and terraform validate in CI before applying any change. Run terraform plan and require human review before terraform apply in production. Prefix all resource names with the environment and project: ${project}_${environment}_resource. Use for_each over count for resource collections to avoid index-shift issues on deletion. Mark sensitive variables with sensitive = true to prevent them appearing in plan output. Use locals{} to avoid repeating expressions; keep variable defaults DRY. Write automated tests for modules using Terratest or terraform test framework. Document every variable and output with a description field. Use workspaces or separate state files per environment, not per-resource file splits.