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

Merge pull request #24771 from bradleypmartin/issue-24198-update-docs-for-map-type 

Update maps docs to reflect v0.12 colon behavior
This commit is contained in:
Daniel Dreier 2020-05-21 14:28:19 -07:00 committed by GitHub
parent 5ef80b35e3 0b45a3c83d
commit 5f80f6d49d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/docs/configuration/types.html.md
View File

@ -95,6 +95,17 @@ The three kinds of collection type in the Terraform language are:
element type as long as every element is the same type. This is for element type as long as every element is the same type. This is for
compatibility with older configurations; for new code, we recommend using compatibility with older configurations; for new code, we recommend using
the full form. the full form.
Maps can be made with braces ({}) and colons (:) or equals signs (=):
{ "foo": "bar", "bar": "baz" } OR { foo = "bar", bar = "baz" }. Quotes
may be omitted on keys, unless the key starts with a number, in which
case quotes are required. Commas are required between key/value pairs
for single line maps. A newline between key/value pairs is sufficient
in multi-line maps.
Note: although colons are valid delimiters between keys and values,
they are currently ignored by `terraform fmt` (whereas `terraform fmt`
will attempt vertically align equals signs).
* `set(...)`: a collection of unique values that do not have any secondary * `set(...)`: a collection of unique values that do not have any secondary
identifiers or ordering. identifiers or ordering.