From 84434410cacfe362a64f21a87d98f9cc5accfa9c Mon Sep 17 00:00:00 2001 From: Chris Stephens Date: Tue, 23 Oct 2018 12:30:00 -0700 Subject: [PATCH] Adding ipv4 range back (#2303) This change would force people to upgrade from legacy networks which are still technically supported in GCP. Since website hasn't moved to magic modules yet this is to accompany https://github.com/GoogleCloudPlatform/magic-modules/pull/599 --- website/docs/r/compute_network.html.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/docs/r/compute_network.html.markdown b/website/docs/r/compute_network.html.markdown index ce049a3c..a77769c8 100644 --- a/website/docs/r/compute_network.html.markdown +++ b/website/docs/r/compute_network.html.markdown @@ -36,6 +36,10 @@ The following arguments are supported: automatically. If set to false, a custom subnetted network will be created that can support `google_compute_subnetwork` resources. Defaults to true. +* `ipv4_range` - (Optional) If set to a CIDR block, uses the legacy VPC API with the + specified range. This API is deprecated. If set, `auto_create_subnetworks` must be + explicitly set to false. + * `routing_mode` - (Optional) Sets the network-wide routing mode for Cloud Routers to use. Accepted values are `"GLOBAL"` or `"REGIONAL"`. Defaults to `"REGIONAL"`. Refer to the [Cloud Router documentation](https://cloud.google.com/router/docs/concepts/overview#dynamic-routing-mode)