From 82a8c9e795b465bc6b36fddbc6179e8f5a7ed262 Mon Sep 17 00:00:00 2001 From: Brian McClain Date: Mon, 25 Mar 2024 17:01:24 -0400 Subject: [PATCH] feedback --- website/docs/language/style.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/language/style.mdx b/website/docs/language/style.mdx index c88098789d..4494883819 100644 --- a/website/docs/language/style.mdx +++ b/website/docs/language/style.mdx @@ -101,6 +101,7 @@ We recommend the following file naming conventions: - `providers.tf`: Contains all `provider` blocks and configuration. - `terraform.tf`: Contains a single `terraform` block which defines your `required_version` and `required_providers`. - `variables.tf`: Contains all variable blocks in alphabetical order. +- `locals.tf`: Contains local values that you reference in multiple files. Refer to [local values](#local-values) for more information. - `override.tf`: Contains override definitions for your configuration. As your codebase grows, limiting it to just these files can become difficult to maintain. If your code becomes hard to navigate due to its size, we recommend that you split the resources and data sources into separate files by logical groups. For example, if your web application requires networking, storage, and compute resources, you might create the following files: