ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #28507 from stevematney/patch-1 

Updating sensitive/nonsensitive docs with v0.14 specifics.
This commit is contained in:
Alisdair McDiarmid 2021-05-14 13:46:12 -04:00 committed by GitHub
parent ef88c54604 e27a927ba4
commit 3e40a9a4eb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/language/functions/nonsensitive.html.md
View File

@ -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.

14
website/docs/language/functions/sensitive.html.md
View File

@ -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 {