public/terraform-provider-google
0
0
Fork 0
mirror of https://github.com/letic/terraform-provider-google.git synced 2024-09-06 17:16:44 +00:00
Code Issues Projects Releases Wiki Activity

Add more acceptance tests, and fix some test cases

Browse Source
This commit is contained in:
Matt Morrison 2016-02-18 00:09:46 +13:00 committed by James Nugent
parent a9c87749be
commit e42ea36d23
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
r/compute_instance_template.html.markdown
View File

@ -85,6 +85,12 @@ The following arguments are supported:
* `network_interface` - (Required) Networks to attach to instances created from this template. * `network_interface` - (Required) Networks to attach to instances created from this template.
This can be specified multiple times for multiple networks. Structure is This can be specified multiple times for multiple networks. Structure is
documented below. documented below.
* `region` - (Optional) An instance template is a global resource that is not bound to a zone
or a region. However, you can still specify some regional resources in an instance template,
which restricts the template to the region where that resource resides. For example, a
custom `subnetwork` resource is tied to a specific region.
Defaults to the region of the Provider if no value is given.
* `automatic_restart` - (Optional, Deprecated - see `scheduling`) * `automatic_restart` - (Optional, Deprecated - see `scheduling`)
Specifies whether the instance should be Specifies whether the instance should be
@ -137,11 +143,12 @@ The `disk` block supports:
The `network_interface` block supports: The `network_interface` block supports:
* `network` - (Optional) The name of the network to attach this interface to. Only use `network` * `network` - (Optional) The name of the network to attach this interface to. Use `network`
attribute for Legacy or Auto subnetted networks, otherwise use `subnetwork` instead. attribute for Legacy or Auto subnetted networks and `subnetwork` for custom subnetted
networks.
* `subnetwork` - (Optional) the name of the subnetwork to attach this interface to. The subnetwork * `subnetwork` - (Optional) the name of the subnetwork to attach this interface to. The subnetwork
must exist in the same region this instance will be created in. Either `network` must exist in the same `region` this instance will be created in. Either `network`
or `subnetwork` must be provided. or `subnetwork` must be provided.
* `access_config` - (Optional) Access configurations, i.e. IPs via which this instance can be * `access_config` - (Optional) Access configurations, i.e. IPs via which this instance can be