Terraform Specifications
Specifications by Category and Module Classification
| Category | Resource | Pattern | Utility |
|---|---|---|---|
| 9 | 8 | 8 | |
| 2 | 2 | 2 | |
| 17 | 12 | 7 | |
| 29 | 29 | 29 | |
| 8 | 6 | 5 | |
| 10 | 10 | 9 | |
| 4 | 4 | 4 | |
| 4 | 4 | 4 | |
| Summary | 83 | 75 | 68 |
How to propose changes to the specifications?
Important
Any updates to existing or new specifications for Terraform must be submitted as a draft for review by Azure Terraform PG/Engineering(@Azure/terraform-avm) and AVM core team(@Azure/avm-core-team).
Important
Provider Versatility: Users have the autonomy to choose between AzureRM, AzAPI, or a combination of both, tailored to the specific complexity of module requirements.