From e61fdcc5c8eecf33e2a2438c09cdce6d88a84532 Mon Sep 17 00:00:00 2001 From: Daniel Bryant Date: Thu, 15 Dec 2016 12:37:13 +0000 Subject: [PATCH] Make clearer that ipv4_range is deprecated (#10749) Removed example code usage that demonstrated deprecated ipv4_range argument, and made clearer that argument is deprecated --- .../docs/providers/google/r/compute_network.html.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/providers/google/r/compute_network.html.markdown b/website/source/docs/providers/google/r/compute_network.html.markdown index a6d469d3a..358b05a25 100644 --- a/website/source/docs/providers/google/r/compute_network.html.markdown +++ b/website/source/docs/providers/google/r/compute_network.html.markdown @@ -14,8 +14,8 @@ Manages a network within GCE. ```js resource "google_compute_network" "default" { - name = "test" - ipv4_range = "10.0.0.0/16" + name = "test" + auto_create_subnetworks = "true" } ``` @@ -37,7 +37,7 @@ The following arguments are supported: * `description` - (Optional) A brief description of this resource. -* `ipv4_range` - (Optional) The IPv4 address range that machines in this network +* `ipv4_range` - (DEPRECATED, Optional) The IPv4 address range that machines in this network are assigned to, represented as a CIDR block. If not set, an auto or custom subnetted network will be created, depending on the value of `auto_create_subnetworks` attribute. This attribute may not be used if