From a83e76125b2ef3aeb6b9672f76e162cadf1d5697 Mon Sep 17 00:00:00 2001 From: Zhuoyun Wei Date: Mon, 25 Jul 2022 12:16:31 -0700 Subject: [PATCH 1/2] docs: fix typo regarding unknown values --- website/docs/language/expressions/references.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/language/expressions/references.mdx b/website/docs/language/expressions/references.mdx index cada96a0c1..67dc4cc292 100644 --- a/website/docs/language/expressions/references.mdx +++ b/website/docs/language/expressions/references.mdx @@ -321,9 +321,9 @@ Terraform cannot predict the value of this id until the object has been created. To allow expressions to still be evaluated during the plan phase, Terraform uses special "unknown value" placeholders for these results. In most cases you don't need to do anything special to deal with these, since the Terraform -language automatically handles unknown values during expressions, so that -for example adding a known value to an unknown value automatically produces -an unknown value as the result. +language automatically handles unknown values in expressions, so that for +example adding a known value to an unknown value automatically produces an +unknown value as the result. However, there are some situations where unknown values _do_ have a significant effect: @@ -349,4 +349,4 @@ effect: types where possible, but incorrect use of such values may not be detected until the apply phase, causing the apply to fail. -Unknown values appear in the `terraform plan` output as `(not yet known)`. +Unknown values appear in the `terraform plan` output as `(known after apply)`. From 7427aa1805b29bb9918d5af75011495e92be8f19 Mon Sep 17 00:00:00 2001 From: Zhuoyun Wei Date: Wed, 27 Jul 2022 21:31:46 -0700 Subject: [PATCH 2/2] Rephrase the paragraph as suggested --- website/docs/language/expressions/references.mdx | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/website/docs/language/expressions/references.mdx b/website/docs/language/expressions/references.mdx index 67dc4cc292..bc4b0c84d1 100644 --- a/website/docs/language/expressions/references.mdx +++ b/website/docs/language/expressions/references.mdx @@ -318,12 +318,10 @@ values are decided dynamically by the remote system. For example, if a particular remote object type is assigned a generated unique id on creation, Terraform cannot predict the value of this id until the object has been created. -To allow expressions to still be evaluated during the plan phase, Terraform -uses special "unknown value" placeholders for these results. In most cases you -don't need to do anything special to deal with these, since the Terraform -language automatically handles unknown values in expressions, so that for -example adding a known value to an unknown value automatically produces an -unknown value as the result. +Terraform uses special unknown value placeholders for information that it +cannot predict during the plan phase. The Terraform language automatically +handles unknown values in expressions. For example, adding a known value to an +unknown value automatically produces an unknown value as a result. However, there are some situations where unknown values _do_ have a significant effect: