docs: consistent use of array configuration syntax

The Terraform configuration syntax defines what arrays are.
Use the word array consistently throughout the documentation
instead of list.

The corresponding JSON datatype is called array as well, and
since the Terraform configuration syntax is interoperable with
JSON it makes sense to use the term array to describe them.
This commit is contained in:
Emil Hessman 2015-01-12 21:10:13 +01:00
parent 975855d950
commit 0daf28f350
2 changed files with 5 additions and 5 deletions

View File

@ -42,18 +42,18 @@ The following arguments are supported:
* `allow` - (Required) Can be specified multiple times for each allow
rule. Each allow block supports fields documented below.
* `source_ranges` - (Optional) A list of source CIDR ranges that this
* `source_ranges` - (Optional) An array of source CIDR ranges that this
firewall applies to.
* `source_tags` - (Optional) A list of source tags that this firewall applies to.
* `source_tags` - (Optional) An array of source tags that this firewall applies to.
* `target_tags` - (Optional) A list of target tags that this firewall applies to.
* `target_tags` - (Optional) An array of target tags that this firewall applies to.
The `allow` block supports:
* `protocol` - (Required) The name of the protocol to allow.
* `ports` - (Optional) List of ports and/or port ranges to allow. This can
* `ports` - (Optional) Array of ports and/or port ranges to allow. This can
only be specified if the protocol is TCP or UDP.
## Attributes Reference

View File

@ -90,7 +90,7 @@ The `network` block supports:
The `service_account` block supports:
* `scopes` - (Required) A list of service scopes. Both OAuth2 URLs and gcloud
* `scopes` - (Required) An array of service scopes. Both OAuth2 URLs and gcloud
short names are supported.
## Attributes Reference