From 3f9abbc30d66f7a143ca62cf5ec89a692ec89cce Mon Sep 17 00:00:00 2001 From: Jacob Tomaw Date: Tue, 3 Nov 2020 08:09:12 -0500 Subject: [PATCH] Remove redundant Local Named Values section The second Local Named Values has a subset of the information the first one has and adds nothing to the documentation other than confusion. --- website/docs/configuration/expressions.html.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/website/docs/configuration/expressions.html.md b/website/docs/configuration/expressions.html.md index 6b4db61115..2aabe44704 100644 --- a/website/docs/configuration/expressions.html.md +++ b/website/docs/configuration/expressions.html.md @@ -321,19 +321,6 @@ Note that unlike `count`, splat expressions are _not_ directly applicable to res * `values(aws_instance.example)[*].id` -### Local Named Values - -Within the bodies of certain expressions, or in some other specific contexts, -there are other named values available beyond the global values listed above. -(For example, the body of a resource block where `count` is set can use a -special `count.index` value.) These local names are described in the -documentation for the specific contexts where they appear. - --> **Note:** Local named values are often referred to as _variables_ or -_temporary variables_ in their documentation. These are not [input -variables](./variables.html); they are just arbitrary names -that temporarily represent a value. - ### Values Not Yet Known When Terraform is planning a set of changes that will apply your configuration,