terraform

ABOUTME: Terraform and Terragrunt skill for production-quality infrastructure code ABOUTME: Enforces HashiCorp best practices, DRY patterns, and security-first design

| DRY | Use modules and Terragrunt to eliminate repetition | | Immutability | Prefer replacement over modification | | Security | No secrets in state; use data sources for sensitive values | | Naming | format | | State | Remote backend always; never local for shared infra | | Modules | Input validation, sensible defaults, documented outputs |

Before EVERY Write or Edit tool call on a .tf or .hcl file:

Guida per scrivere codice dell'infrastruttura Terraform e Terragrunt di qualità produttiva seguendo le best practice di HashiCorp e della community. Trigger su "terraform", "terragrunt", "tf", "hcl", "infrastructure as code", "iac", "aws terraform", "gcp terraform", "azure terraform", "terraform module", "terraform state", "terraform plan", "terraform apply", "terraform init", "terraform workspace", "terraform backend", "terraform provider", "terraform resources", "terraform data", "terraform variable", "terraform output", "terraform locals", "terraform for_each", "terraform count", "terraformdynamic", "tfvars", "terraform validate", "terraform fmt", "tflint", "terraform import", "terraform destroy", "remote state", "statelocking", "terraform cloud", "opentofu". PROATTIVO: DEVE essere invocato durante la scrittura di QUALSIASI file .tf o .hcl. Fonte: mauromedda/agent-toolkit.