From e27a927ba4975a378d0260b8f20cd793bbbd2e2d Mon Sep 17 00:00:00 2001 From: Steve Matney Date: Fri, 14 May 2021 10:27:13 -0600 Subject: [PATCH] Updating sensitive and nonsensitive docs with correct v0.15 info. --- .../docs/language/functions/nonsensitive.html.md | 2 +- website/docs/language/functions/sensitive.html.md | 14 +++++++------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/website/docs/language/functions/nonsensitive.html.md b/website/docs/language/functions/nonsensitive.html.md index 8458f4e70..a8143c935 100644 --- a/website/docs/language/functions/nonsensitive.html.md +++ b/website/docs/language/functions/nonsensitive.html.md @@ -8,7 +8,7 @@ description: |- # `nonsensitive` Function --> **Note:** This function is only available in Terraform v0.14 and later. +-> **Note:** This function is only available in Terraform v0.15 and later. `nonsensitive` takes a sensitive value and returns a copy of that value with the sensitive marking removed, thereby exposing the sensitive value. diff --git a/website/docs/language/functions/sensitive.html.md b/website/docs/language/functions/sensitive.html.md index bcc9bfecf..03ab6bd96 100644 --- a/website/docs/language/functions/sensitive.html.md +++ b/website/docs/language/functions/sensitive.html.md @@ -8,20 +8,20 @@ description: |- # `sensitive` Function --> **Note:** This function is only available in Terraform v0.14 and later. +-> **Note:** This function is only available in Terraform v0.15 and later. `sensitive` takes any value and returns a copy of it marked so that Terraform will treat it as sensitive, with the same meaning and behavior as for [sensitive input variables](/docs/language/values/variables.html#suppressing-values-in-cli-output). -Whereever possible we recommend marking your input variable and/or output value -declarations as sensitive directly, instead of using this function, because -in that case you can be sure that there is no way to refer to those values -without Terraform automatically considering them as sensitive. +Wherever possible we recommend marking your input variable and/or output value +declarations as sensitive directly, instead of using this function, because in +that case you can be sure that there is no way to refer to those values without +Terraform automatically considering them as sensitive. The `sensitive` function might be useful in some less-common situations where a -sensitive value arises from a definition _within_ your module, such as if -you've loaded sensitive data from a file on disk as part of your configuration: +sensitive value arises from a definition _within_ your module, such as if you've +loaded sensitive data from a file on disk as part of your configuration: ``` locals {