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

website: for_each doesn't implicitly convert to set (#26450) 

The documentation states that an explicit type conversion to set is needed, but it does not say why implicit type conversion does not work. 

Co-authored-by: Nick Fagerlund <nick@hashicorp.com>
This commit is contained in:
timvandamme 2020-11-02 20:13:51 +01:00 committed by GitHub
parent 3ed08e3566
commit fbf267fbfd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/configuration/resources.html.md
View File

@ -446,7 +446,11 @@ configuration is applied (such as a unique ID generated by the remote API when
an object is created). an object is created).
The `for_each` value must be a map or set with one element per desired The `for_each` value must be a map or set with one element per desired
resource instance. If you need to declare resource instances based on a nested resource instance. When providing a set, you must use an expression that
explicitly returns a set value, like the [`toset`](/docs/configuration/functions/toset.html)
function; to prevent unwanted surprises during conversion, the `for_each`
argument does not implicitly convert lists or tuples to sets.
If you need to declare resource instances based on a nested
data structure or combinations of elements from multiple data structures you data structure or combinations of elements from multiple data structures you
can use Terraform expressions and functions to derive a suitable value. can use Terraform expressions and functions to derive a suitable value.
For example: For example: