core.file_naming¶
Enforces that different type of terraform-resources are written in the correct files
Why¶
Consistent file-structure across multiple projects. Keeps scalability and error analysis simple.
Example "I want to see resources that I load from external (data-resources). I can just open data.tf"
Mapping TF-Type to File¶
| Type | Filename |
|---|---|
| output | outputs.tf |
| variable | variables.tf |
| locals | locals.tf |
| provider | providers.tf |
| data | data.tf |
Mapping of Terraform Block¶
The Terraform Block is separated in different files based on Blocks and Attributes. In general, the "terraform"-Block is allowed to be in following files:
- backend.tf
- terraform.tf
| Filename | Blocks | Attributes |
|---|---|---|
| backend.tf | cloud, backend | |
| terraform.tf | required_provider ,provider_meta | required_version,experiments |
Configuration¶
There is currently no configuration flags for that rule, beside the option to enable or disable the rule