Terraform Rules
Define and provision cloud infrastructure as code. Plan, apply, and manage resources across any cloud provider.
3 rules
Terraform Naming Conventions
Beginner
Enforce consistent naming across Terraform configurations — resource names, variable names, output names, file organization, and cloud resource naming patterns.
globs: **/*.tf, **/*.tfvars, **/terraform/**, **/infrastructure/**
naming-conventions, snake-case, file-organization, terraform-standards
View Rule
Mandatory Resource Tagging
Beginner
Enforce mandatory tags on all Terraform-managed cloud resources for cost allocation, ownership tracking, environment identification, and compliance requirements.
globs: **/*.tf, **/*.tfvars, **/terraform/**, **/infrastructure/**
tagging, cost-allocation, governance, compliance
View Rule
Remote State Backend Configuration
Intermediate
Every Terraform project must use a remote backend with state locking and encryption — never local state files, never state in version control, always encrypted at rest.
globs: **/*.tf, **/backend.tf, **/terraform/**, **/infrastructure/**
state-backend, remote-state, encryption, state-locking
View Rule