Promote field compute_instance.scheduling.min_node_cpus and related f…

…ields to ga (#4593) (#504) Signed-off-by: Modular Magician <[email protected]>
modular-magician · Mar 15, 2021 · a6829b3 · a6829b3
1 parent 773db72
commit a6829b3
Show file tree

Hide file tree

Showing 7 changed files with 14 additions and 14 deletions.
diff --git a/docs/resources/google_compute_backend_bucket.md b/docs/resources/google_compute_backend_bucket.md
@@ -34,7 +34,7 @@ Properties that can be accessed from the `google_compute_backend_bucket` resourc
 
     * `signed_url_cache_max_age_sec`: Maximum number of seconds the response to a signed URL request will be considered fresh. After this time period, the response will be revalidated before being served. When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a "Cache-Control: public, max-age=[TTL]" header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered.
 
-    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses  that do not have an existing valid TTL (max-age or s-max-age).
+    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses that do not have an existing valid TTL (max-age or s-max-age).
 
     * `max_ttl`: (Beta only) Specifies the maximum allowed TTL for cached content served by this origin.
 
@@ -54,7 +54,7 @@ Properties that can be accessed from the `google_compute_backend_bucket` resourc
       * FORCE_CACHE_ALL
       * CACHE_ALL_STATIC
 
-    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache. 
+    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
 
   * `custom_response_headers`: (Beta only) Headers that the HTTP/S load balancer should add to proxied responses.
 

diff --git a/docs/resources/google_compute_backend_service.md b/docs/resources/google_compute_backend_service.md
@@ -112,7 +112,7 @@ Properties that can be accessed from the `google_compute_backend_service` resour
 
     * `signed_url_cache_max_age_sec`: Maximum number of seconds the response to a signed URL request will be considered fresh, defaults to 1hr (3600s). After this time period, the response will be revalidated before being served.  When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a "Cache-Control: public, max-age=[TTL]" header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered.
 
-    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses  that do not have an existing valid TTL (max-age or s-max-age).
+    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses that do not have an existing valid TTL (max-age or s-max-age).
 
     * `max_ttl`: (Beta only) Specifies the maximum allowed TTL for cached content served by this origin.
 
@@ -132,7 +132,7 @@ Properties that can be accessed from the `google_compute_backend_service` resour
       * FORCE_CACHE_ALL
       * CACHE_ALL_STATIC
 
-    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache. 
+    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
 
   * `connection_draining`: Settings for connection draining
 

diff --git a/docs/resources/google_compute_disk.md b/docs/resources/google_compute_disk.md
@@ -110,7 +110,7 @@ Properties that can be accessed from the `google_compute_disk` resource:
 
     * `sha256`: The RFC 4648 base64 encoded SHA-256 hash of the customer-supplied encryption key that protects this resource.
 
-    * `kms_key_service_account`: The service account used for the encryption request for the given KMS key.  If absent, the Compute Engine Service Agent service account is used.
+    * `kms_key_service_account`: The service account used for the encryption request for the given KMS key. If absent, the Compute Engine Service Agent service account is used.
 
   * `source_snapshot_id`: The unique ID of the snapshot used to create this disk. This value identifies the exact snapshot that was used to create this persistent disk. For example, if you created the persistent disk from a snapshot that was later deleted and recreated under the same name, the source snapshot ID would identify the exact version of the snapshot that was used.
 

diff --git a/docs/resources/google_compute_health_check.md b/docs/resources/google_compute_health_check.md
@@ -164,7 +164,7 @@ Properties that can be accessed from the `google_compute_health_check` resource:
 
   * `grpc_health_check`: A nested object resource
 
-    * `port`: The port number for the health check request.  Must be specified if portName and portSpecification are not set  or if port_specification is USE_FIXED_PORT. Valid values are 1 through 65535.
+    * `port`: The port number for the health check request. Must be specified if portName and portSpecification are not set or if port_specification is USE_FIXED_PORT. Valid values are 1 through 65535.
 
     * `port_name`: Port name as defined in InstanceGroup#NamedPort#name. If both port and port_name are defined, port takes precedence.
 
@@ -174,7 +174,7 @@ Properties that can be accessed from the `google_compute_health_check` resource:
       * USE_NAMED_PORT
       * USE_SERVING_PORT
 
-    * `grpc_service_name`: The gRPC service name for the health check.  The value of grpcServiceName has the following meanings by convention:   - Empty serviceName means the overall status of all services at the backend.   - Non-empty serviceName means the health of that gRPC service, as defined by the owner of the service. The grpcServiceName can only be ASCII.
+    * `grpc_service_name`: The gRPC service name for the health check. The value of grpcServiceName has the following meanings by convention:   - Empty serviceName means the overall status of all services at the backend.   - Non-empty serviceName means the health of that gRPC service, as defined by the owner of the service. The grpcServiceName can only be ASCII.
 
   * `log_config`: (Beta only) Configure logging on this health check.
 

diff --git a/docs/resources/google_compute_node_template.md b/docs/resources/google_compute_node_template.md
@@ -45,14 +45,14 @@ Properties that can be accessed from the `google_compute_node_template` resource
 
     * `local_ssd`: Use local SSD
 
-  * `server_binding`: (Beta only) The server binding policy for nodes using this template. Determines where the nodes should restart following a maintenance event.
+  * `server_binding`: The server binding policy for nodes using this template. Determines where the nodes should restart following a maintenance event.
 
     * `type`: Type of server binding policy. If `RESTART_NODE_ON_ANY_SERVER`, nodes using this template will restart on any physical server following a maintenance event.  If `RESTART_NODE_ON_MINIMAL_SERVER`, nodes using this template will restart on the same physical server following a maintenance event, instead of being live migrated to or restarted on a new physical server. This option may be useful if you are using software licenses tied to the underlying server characteristics such as physical sockets or cores, to avoid the need for additional licenses when maintenance occurs. However, VMs on such nodes will experience outages while maintenance is applied.
     Possible values:
       * RESTART_NODE_ON_ANY_SERVER
       * RESTART_NODE_ON_MINIMAL_SERVERS
 
-  * `cpu_overcommit_type`: (Beta only) CPU overcommit.
+  * `cpu_overcommit_type`: CPU overcommit.
   Possible values:
     * ENABLED
     * NONE

diff --git a/docs/resources/google_compute_node_templates.md b/docs/resources/google_compute_node_templates.md
@@ -28,8 +28,8 @@ See [google_compute_node_template.md](google_compute_node_template.md) for more
   * `node_affinity_labels`: an array of `google_compute_node_template` node_affinity_labels
   * `node_types`: an array of `google_compute_node_template` node_type
   * `node_type_flexibilities`: an array of `google_compute_node_template` node_type_flexibility
-  * `server_bindings`: (Beta only) an array of `google_compute_node_template` server_binding
-  * `cpu_overcommit_types`: (Beta only) an array of `google_compute_node_template` cpu_overcommit_type
+  * `server_bindings`: an array of `google_compute_node_template` server_binding
+  * `cpu_overcommit_types`: an array of `google_compute_node_template` cpu_overcommit_type
   * `regions`: an array of `google_compute_node_template` region
 
 ## Filter Criteria

diff --git a/docs/resources/google_compute_region_backend_service.md b/docs/resources/google_compute_region_backend_service.md
@@ -112,7 +112,7 @@ Properties that can be accessed from the `google_compute_region_backend_service`
 
     * `signed_url_cache_max_age_sec`: Maximum number of seconds the response to a signed URL request will be considered fresh, defaults to 1hr (3600s). After this time period, the response will be revalidated before being served.  When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a "Cache-Control: public, max-age=[TTL]" header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered.
 
-    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses  that do not have an existing valid TTL (max-age or s-max-age).
+    * `default_ttl`: (Beta only) Specifies the default TTL for cached content served by this origin for responses that do not have an existing valid TTL (max-age or s-max-age).
 
     * `max_ttl`: (Beta only) Specifies the maximum allowed TTL for cached content served by this origin.
 
@@ -132,7 +132,7 @@ Properties that can be accessed from the `google_compute_region_backend_service`
       * FORCE_CACHE_ALL
       * CACHE_ALL_STATIC
 
-    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache. 
+    * `serve_while_stale`: (Beta only) Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
 
   * `connection_draining`: Settings for connection draining
 
@@ -154,7 +154,7 @@ Properties that can be accessed from the `google_compute_region_backend_service`
 
   * `fingerprint`: Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
 
-  * `health_checks`: The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified.   A health check must be specified unless the backend service uses an internet or serverless NEG as a backend.
+  * `health_checks`: The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified.  A health check must be specified unless the backend service uses an internet or serverless NEG as a backend.
 
   * `id`: The unique identifier for the resource.