google-cloud-compute-v1 0.3.0 → 1.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.yardopts +1 -1
- data/AUTHENTICATION.md +7 -25
- data/README.md +4 -4
- data/lib/google/cloud/compute/v1/accelerator_types/rest/client.rb +4 -24
- data/lib/google/cloud/compute/v1/addresses/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/autoscalers/rest/client.rb +8 -44
- data/lib/google/cloud/compute/v1/backend_buckets/rest/client.rb +85 -42
- data/lib/google/cloud/compute/v1/backend_buckets/rest/service_stub.rb +46 -0
- data/lib/google/cloud/compute/v1/backend_services/rest/client.rb +91 -66
- data/lib/google/cloud/compute/v1/backend_services/rest/service_stub.rb +46 -0
- data/lib/google/cloud/compute/v1/compute_pb.rb +8335 -7443
- data/lib/google/cloud/compute/v1/disk_types/rest/client.rb +4 -24
- data/lib/google/cloud/compute/v1/disks/rest/client.rb +12 -60
- data/lib/google/cloud/compute/v1/external_vpn_gateways/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/firewall_policies/rest/client.rb +13 -63
- data/lib/google/cloud/compute/v1/firewalls/rest/client.rb +6 -32
- data/lib/google/cloud/compute/v1/forwarding_rules/rest/client.rb +9 -49
- data/lib/google/cloud/compute/v1/global_addresses/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/global_forwarding_rules/rest/client.rb +7 -33
- data/lib/google/cloud/compute/v1/global_network_endpoint_groups/rest/client.rb +8 -44
- data/lib/google/cloud/compute/v1/global_operations/rest/client.rb +6 -30
- data/lib/google/cloud/compute/v1/global_organization_operations/rest/client.rb +2 -12
- data/lib/google/cloud/compute/v1/global_public_delegated_prefixes/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/health_checks/rest/client.rb +8 -44
- data/lib/google/cloud/compute/v1/image_family_views/credentials.rb +53 -0
- data/lib/google/cloud/compute/v1/image_family_views/rest/client.rb +318 -0
- data/lib/google/cloud/compute/v1/image_family_views/rest/service_stub.rb +89 -0
- data/lib/google/cloud/compute/v1/image_family_views/rest.rb +33 -0
- data/lib/google/cloud/compute/v1/image_family_views.rb +44 -0
- data/lib/google/cloud/compute/v1/images/rest/client.rb +7 -35
- data/lib/google/cloud/compute/v1/instance_group_managers/rest/client.rb +30 -150
- data/lib/google/cloud/compute/v1/instance_groups/rest/client.rb +16 -72
- data/lib/google/cloud/compute/v1/instance_templates/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/instances/rest/client.rb +272 -197
- data/lib/google/cloud/compute/v1/instances/rest/service_stub.rb +134 -0
- data/lib/google/cloud/compute/v1/interconnect_attachments/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/interconnect_locations/rest/client.rb +2 -12
- data/lib/google/cloud/compute/v1/interconnects/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/license_codes/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/licenses/rest/client.rb +11 -29
- data/lib/google/cloud/compute/v1/machine_images/credentials.rb +52 -0
- data/lib/google/cloud/compute/v1/machine_images/rest/client.rb +777 -0
- data/lib/google/cloud/compute/v1/machine_images/rest/service_stub.rb +363 -0
- data/lib/google/cloud/compute/v1/machine_images/rest.rb +33 -0
- data/lib/google/cloud/compute/v1/machine_images.rb +44 -0
- data/lib/google/cloud/compute/v1/machine_types/rest/client.rb +4 -24
- data/lib/google/cloud/compute/v1/network_endpoint_groups/rest/client.rb +10 -56
- data/lib/google/cloud/compute/v1/networks/rest/client.rb +14 -61
- data/lib/google/cloud/compute/v1/node_groups/rest/client.rb +12 -66
- data/lib/google/cloud/compute/v1/node_templates/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/node_types/rest/client.rb +4 -24
- data/lib/google/cloud/compute/v1/packet_mirrorings/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/projects/rest/client.rb +15 -71
- data/lib/google/cloud/compute/v1/public_advertised_prefixes/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/public_delegated_prefixes/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/region_autoscalers/rest/client.rb +6 -32
- data/lib/google/cloud/compute/v1/region_backend_services/rest/client.rb +9 -35
- data/lib/google/cloud/compute/v1/region_commitments/rest/client.rb +88 -30
- data/lib/google/cloud/compute/v1/region_commitments/rest/service_stub.rb +48 -0
- data/lib/google/cloud/compute/v1/region_disk_types/rest/client.rb +2 -12
- data/lib/google/cloud/compute/v1/region_disks/rest/client.rb +10 -48
- data/lib/google/cloud/compute/v1/region_health_check_services/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/region_health_checks/rest/client.rb +6 -32
- data/lib/google/cloud/compute/v1/region_instance_group_managers/rest/client.rb +27 -133
- data/lib/google/cloud/compute/v1/region_instance_groups/rest/client.rb +5 -29
- data/lib/google/cloud/compute/v1/region_instances/rest/client.rb +1 -5
- data/lib/google/cloud/compute/v1/region_network_endpoint_groups/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/region_notification_endpoints/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/region_operations/rest/client.rb +3 -17
- data/lib/google/cloud/compute/v1/region_ssl_certificates/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/region_target_http_proxies/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/region_target_https_proxies/rest/client.rb +6 -32
- data/lib/google/cloud/compute/v1/region_url_maps/rest/client.rb +2 -12
- data/lib/google/cloud/compute/v1/regions/rest/client.rb +4 -14
- data/lib/google/cloud/compute/v1/reservations/rest/client.rb +89 -39
- data/lib/google/cloud/compute/v1/reservations/rest/service_stub.rb +48 -0
- data/lib/google/cloud/compute/v1/resource_policies/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/routers/rest/client.rb +10 -56
- data/lib/google/cloud/compute/v1/routes/rest/client.rb +4 -22
- data/lib/google/cloud/compute/v1/security_policies/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/service_attachments/credentials.rb +52 -0
- data/lib/google/cloud/compute/v1/service_attachments/rest/client.rb +954 -0
- data/lib/google/cloud/compute/v1/service_attachments/rest/service_stub.rb +458 -0
- data/lib/google/cloud/compute/v1/service_attachments/rest.rb +33 -0
- data/lib/google/cloud/compute/v1/service_attachments.rb +44 -0
- data/lib/google/cloud/compute/v1/snapshots/rest/client.rb +79 -20
- data/lib/google/cloud/compute/v1/snapshots/rest/service_stub.rb +46 -0
- data/lib/google/cloud/compute/v1/ssl_certificates/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/ssl_policies/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/subnetworks/rest/client.rb +11 -61
- data/lib/google/cloud/compute/v1/target_grpc_proxies/rest/client.rb +5 -27
- data/lib/google/cloud/compute/v1/target_http_proxies/rest/client.rb +9 -45
- data/lib/google/cloud/compute/v1/target_https_proxies/rest/client.rb +12 -60
- data/lib/google/cloud/compute/v1/target_instances/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/target_pools/rest/client.rb +11 -59
- data/lib/google/cloud/compute/v1/target_ssl_proxies/rest/client.rb +8 -42
- data/lib/google/cloud/compute/v1/target_tcp_proxies/rest/client.rb +6 -32
- data/lib/google/cloud/compute/v1/target_vpn_gateways/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/url_maps/rest/client.rb +10 -52
- data/lib/google/cloud/compute/v1/version.rb +1 -1
- data/lib/google/cloud/compute/v1/vpn_gateways/rest/client.rb +7 -39
- data/lib/google/cloud/compute/v1/vpn_tunnels/rest/client.rb +6 -34
- data/lib/google/cloud/compute/v1/zone_operations/rest/client.rb +3 -17
- data/lib/google/cloud/compute/v1/zones/rest/client.rb +2 -12
- data/lib/google/cloud/compute/v1.rb +3 -0
- data/proto_docs/README.md +1 -1
- data/proto_docs/google/api/field_behavior.rb +6 -0
- data/proto_docs/google/api/resource.rb +10 -71
- data/proto_docs/google/cloud/compute/v1/compute.rb +20013 -21099
- data/proto_docs/google/cloud/extended_operations.rb +51 -0
- metadata +34 -4
@@ -173,23 +173,13 @@ module Google
|
|
173
173
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
174
174
|
#
|
175
175
|
# @param filter [::String]
|
176
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
177
|
-
#
|
178
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
179
|
-
#
|
180
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
181
|
-
#
|
182
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
176
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
183
177
|
# @param include_all_scopes [::Boolean]
|
184
178
|
# Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
|
185
179
|
# @param max_results [::Integer]
|
186
180
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
187
181
|
# @param order_by [::String]
|
188
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
189
|
-
#
|
190
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
191
|
-
#
|
192
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
182
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
193
183
|
# @param page_token [::String]
|
194
184
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
195
185
|
# @param project [::String]
|
@@ -263,11 +253,7 @@ module Google
|
|
263
253
|
# @param project [::String]
|
264
254
|
# Project ID for this request.
|
265
255
|
# @param request_id [::String]
|
266
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
267
|
-
#
|
268
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
269
|
-
#
|
270
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
256
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
271
257
|
# @param zone [::String]
|
272
258
|
# The name of the zone where the network endpoint group is located. It should comply with RFC1035.
|
273
259
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -335,11 +321,7 @@ module Google
|
|
335
321
|
# @param project [::String]
|
336
322
|
# Project ID for this request.
|
337
323
|
# @param request_id [::String]
|
338
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
339
|
-
#
|
340
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
341
|
-
#
|
342
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
324
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
343
325
|
# @param zone [::String]
|
344
326
|
# The name of the zone where the network endpoint group is located. It should comply with RFC1035.
|
345
327
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -409,11 +391,7 @@ module Google
|
|
409
391
|
# @param project [::String]
|
410
392
|
# Project ID for this request.
|
411
393
|
# @param request_id [::String]
|
412
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
413
|
-
#
|
414
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
415
|
-
#
|
416
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
394
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
417
395
|
# @param zone [::String]
|
418
396
|
# The name of the zone where the network endpoint group is located. It should comply with RFC1035.
|
419
397
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -546,11 +524,7 @@ module Google
|
|
546
524
|
# @param project [::String]
|
547
525
|
# Project ID for this request.
|
548
526
|
# @param request_id [::String]
|
549
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
550
|
-
#
|
551
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
552
|
-
#
|
553
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
527
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
554
528
|
# @param zone [::String]
|
555
529
|
# The name of the zone where you want to create the network endpoint group. It should comply with RFC1035.
|
556
530
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -614,21 +588,11 @@ module Google
|
|
614
588
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
615
589
|
#
|
616
590
|
# @param filter [::String]
|
617
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
618
|
-
#
|
619
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
620
|
-
#
|
621
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
622
|
-
#
|
623
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
591
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
624
592
|
# @param max_results [::Integer]
|
625
593
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
626
594
|
# @param order_by [::String]
|
627
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
628
|
-
#
|
629
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
630
|
-
#
|
631
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
595
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
632
596
|
# @param page_token [::String]
|
633
597
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
634
598
|
# @param project [::String]
|
@@ -698,13 +662,7 @@ module Google
|
|
698
662
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
699
663
|
#
|
700
664
|
# @param filter [::String]
|
701
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
702
|
-
#
|
703
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
704
|
-
#
|
705
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
706
|
-
#
|
707
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
665
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
708
666
|
# @param max_results [::Integer]
|
709
667
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
710
668
|
# @param network_endpoint_group [::String]
|
@@ -712,11 +670,7 @@ module Google
|
|
712
670
|
# @param network_endpoint_groups_list_endpoints_request_resource [::Google::Cloud::Compute::V1::NetworkEndpointGroupsListEndpointsRequest, ::Hash]
|
713
671
|
# The body resource for this request
|
714
672
|
# @param order_by [::String]
|
715
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
716
|
-
#
|
717
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
718
|
-
#
|
719
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
673
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
720
674
|
# @param page_token [::String]
|
721
675
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
722
676
|
# @param project [::String]
|
@@ -186,11 +186,7 @@ module Google
|
|
186
186
|
# @param project [::String]
|
187
187
|
# Project ID for this request.
|
188
188
|
# @param request_id [::String]
|
189
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
190
|
-
#
|
191
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
192
|
-
#
|
193
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
189
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
194
190
|
# @yield [result, response] Access the result along with the Faraday response object
|
195
191
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
196
192
|
# @yieldparam response [::Faraday::Response]
|
@@ -256,11 +252,7 @@ module Google
|
|
256
252
|
# @param project [::String]
|
257
253
|
# Project ID for this request.
|
258
254
|
# @param request_id [::String]
|
259
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
260
|
-
#
|
261
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
262
|
-
#
|
263
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
255
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
264
256
|
# @yield [result, response] Access the result along with the Faraday response object
|
265
257
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
266
258
|
# @yieldparam response [::Faraday::Response]
|
@@ -452,11 +444,7 @@ module Google
|
|
452
444
|
# @param project [::String]
|
453
445
|
# Project ID for this request.
|
454
446
|
# @param request_id [::String]
|
455
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
456
|
-
#
|
457
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
458
|
-
#
|
459
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
447
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
460
448
|
# @yield [result, response] Access the result along with the Faraday response object
|
461
449
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
462
450
|
# @yieldparam response [::Faraday::Response]
|
@@ -518,21 +506,11 @@ module Google
|
|
518
506
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
519
507
|
#
|
520
508
|
# @param filter [::String]
|
521
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
522
|
-
#
|
523
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
524
|
-
#
|
525
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
526
|
-
#
|
527
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
509
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
528
510
|
# @param max_results [::Integer]
|
529
511
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
530
512
|
# @param order_by [::String]
|
531
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
532
|
-
#
|
533
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
534
|
-
#
|
535
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
513
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
536
514
|
# @param page_token [::String]
|
537
515
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
538
516
|
# @param project [::String]
|
@@ -599,26 +577,17 @@ module Google
|
|
599
577
|
# least one keyword argument is required. To specify no parameters, or to keep all
|
600
578
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
601
579
|
#
|
602
|
-
# @param direction [::
|
580
|
+
# @param direction [::String]
|
603
581
|
# The direction of the exchanged routes.
|
582
|
+
# Check the Direction enum for the list of possible values.
|
604
583
|
# @param filter [::String]
|
605
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
606
|
-
#
|
607
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
608
|
-
#
|
609
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
610
|
-
#
|
611
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
584
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
612
585
|
# @param max_results [::Integer]
|
613
586
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
614
587
|
# @param network [::String]
|
615
588
|
# Name of the network for this request.
|
616
589
|
# @param order_by [::String]
|
617
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
618
|
-
#
|
619
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
620
|
-
#
|
621
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
590
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
622
591
|
# @param page_token [::String]
|
623
592
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
624
593
|
# @param peering_name [::String]
|
@@ -696,11 +665,7 @@ module Google
|
|
696
665
|
# @param project [::String]
|
697
666
|
# Project ID for this request.
|
698
667
|
# @param request_id [::String]
|
699
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
700
|
-
#
|
701
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
702
|
-
#
|
703
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
668
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
704
669
|
# @yield [result, response] Access the result along with the Faraday response object
|
705
670
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
706
671
|
# @yieldparam response [::Faraday::Response]
|
@@ -768,11 +733,7 @@ module Google
|
|
768
733
|
# @param project [::String]
|
769
734
|
# Project ID for this request.
|
770
735
|
# @param request_id [::String]
|
771
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
772
|
-
#
|
773
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
774
|
-
#
|
775
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
736
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
776
737
|
# @yield [result, response] Access the result along with the Faraday response object
|
777
738
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
778
739
|
# @yieldparam response [::Faraday::Response]
|
@@ -838,11 +799,7 @@ module Google
|
|
838
799
|
# @param project [::String]
|
839
800
|
# Project ID for this request.
|
840
801
|
# @param request_id [::String]
|
841
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
842
|
-
#
|
843
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
844
|
-
#
|
845
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
802
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
846
803
|
# @yield [result, response] Access the result along with the Faraday response object
|
847
804
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
848
805
|
# @yieldparam response [::Faraday::Response]
|
@@ -884,7 +841,7 @@ module Google
|
|
884
841
|
end
|
885
842
|
|
886
843
|
##
|
887
|
-
# Updates the specified network peering with the data included in the request
|
844
|
+
# Updates the specified network peering with the data included in the request. You can only modify the NetworkPeering.export_custom_routes field and the NetworkPeering.import_custom_routes field.
|
888
845
|
#
|
889
846
|
# @overload update_peering(request, options = nil)
|
890
847
|
# Pass arguments to `update_peering` via a request object, either of type
|
@@ -910,11 +867,7 @@ module Google
|
|
910
867
|
# @param project [::String]
|
911
868
|
# Project ID for this request.
|
912
869
|
# @param request_id [::String]
|
913
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
914
|
-
#
|
915
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
916
|
-
#
|
917
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
870
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
918
871
|
# @yield [result, response] Access the result along with the Faraday response object
|
919
872
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
920
873
|
# @yieldparam response [::Faraday::Response]
|
@@ -190,11 +190,7 @@ module Google
|
|
190
190
|
# @param project [::String]
|
191
191
|
# Project ID for this request.
|
192
192
|
# @param request_id [::String]
|
193
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
194
|
-
#
|
195
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
196
|
-
#
|
197
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
193
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
198
194
|
# @param zone [::String]
|
199
195
|
# The name of the zone for this request.
|
200
196
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -258,23 +254,13 @@ module Google
|
|
258
254
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
259
255
|
#
|
260
256
|
# @param filter [::String]
|
261
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
262
|
-
#
|
263
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
264
|
-
#
|
265
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
266
|
-
#
|
267
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
257
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
268
258
|
# @param include_all_scopes [::Boolean]
|
269
259
|
# Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
|
270
260
|
# @param max_results [::Integer]
|
271
261
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
272
262
|
# @param order_by [::String]
|
273
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
274
|
-
#
|
275
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
276
|
-
#
|
277
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
263
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
278
264
|
# @param page_token [::String]
|
279
265
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
280
266
|
# @param project [::String]
|
@@ -346,11 +332,7 @@ module Google
|
|
346
332
|
# @param project [::String]
|
347
333
|
# Project ID for this request.
|
348
334
|
# @param request_id [::String]
|
349
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
350
|
-
#
|
351
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
352
|
-
#
|
353
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
335
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
354
336
|
# @param zone [::String]
|
355
337
|
# The name of the zone for this request.
|
356
338
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -420,11 +402,7 @@ module Google
|
|
420
402
|
# @param project [::String]
|
421
403
|
# Project ID for this request.
|
422
404
|
# @param request_id [::String]
|
423
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
424
|
-
#
|
425
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
426
|
-
#
|
427
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
405
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
428
406
|
# @param zone [::String]
|
429
407
|
# The name of the zone for this request.
|
430
408
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -626,11 +604,7 @@ module Google
|
|
626
604
|
# @param project [::String]
|
627
605
|
# Project ID for this request.
|
628
606
|
# @param request_id [::String]
|
629
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
630
|
-
#
|
631
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
632
|
-
#
|
633
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
607
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
634
608
|
# @param zone [::String]
|
635
609
|
# The name of the zone for this request.
|
636
610
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -694,21 +668,11 @@ module Google
|
|
694
668
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
695
669
|
#
|
696
670
|
# @param filter [::String]
|
697
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
698
|
-
#
|
699
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
700
|
-
#
|
701
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
702
|
-
#
|
703
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
671
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
704
672
|
# @param max_results [::Integer]
|
705
673
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
706
674
|
# @param order_by [::String]
|
707
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
708
|
-
#
|
709
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
710
|
-
#
|
711
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
675
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
712
676
|
# @param page_token [::String]
|
713
677
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
714
678
|
# @param project [::String]
|
@@ -778,23 +742,13 @@ module Google
|
|
778
742
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
779
743
|
#
|
780
744
|
# @param filter [::String]
|
781
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
782
|
-
#
|
783
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
784
|
-
#
|
785
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
786
|
-
#
|
787
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
745
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
788
746
|
# @param max_results [::Integer]
|
789
747
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
790
748
|
# @param node_group [::String]
|
791
749
|
# Name of the NodeGroup resource whose nodes you want to list.
|
792
750
|
# @param order_by [::String]
|
793
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
794
|
-
#
|
795
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
796
|
-
#
|
797
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
751
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
798
752
|
# @param page_token [::String]
|
799
753
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
800
754
|
# @param project [::String]
|
@@ -870,11 +824,7 @@ module Google
|
|
870
824
|
# @param project [::String]
|
871
825
|
# Project ID for this request.
|
872
826
|
# @param request_id [::String]
|
873
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
874
|
-
#
|
875
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
876
|
-
#
|
877
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
827
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
878
828
|
# @param zone [::String]
|
879
829
|
# The name of the zone for this request.
|
880
830
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -1011,11 +961,7 @@ module Google
|
|
1011
961
|
# @param project [::String]
|
1012
962
|
# Project ID for this request.
|
1013
963
|
# @param request_id [::String]
|
1014
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
1015
|
-
#
|
1016
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
1017
|
-
#
|
1018
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
964
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
1019
965
|
# @param zone [::String]
|
1020
966
|
# The name of the zone for this request.
|
1021
967
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -174,23 +174,13 @@ module Google
|
|
174
174
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
175
175
|
#
|
176
176
|
# @param filter [::String]
|
177
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
178
|
-
#
|
179
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
180
|
-
#
|
181
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
182
|
-
#
|
183
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
177
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
184
178
|
# @param include_all_scopes [::Boolean]
|
185
179
|
# Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
|
186
180
|
# @param max_results [::Integer]
|
187
181
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
188
182
|
# @param order_by [::String]
|
189
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
190
|
-
#
|
191
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
192
|
-
#
|
193
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
183
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
194
184
|
# @param page_token [::String]
|
195
185
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
196
186
|
# @param project [::String]
|
@@ -264,11 +254,7 @@ module Google
|
|
264
254
|
# @param region [::String]
|
265
255
|
# The name of the region for this request.
|
266
256
|
# @param request_id [::String]
|
267
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
268
|
-
#
|
269
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
270
|
-
#
|
271
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
257
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
272
258
|
# @yield [result, response] Access the result along with the Faraday response object
|
273
259
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
274
260
|
# @yieldparam response [::Faraday::Response]
|
@@ -468,11 +454,7 @@ module Google
|
|
468
454
|
# @param region [::String]
|
469
455
|
# The name of the region for this request.
|
470
456
|
# @param request_id [::String]
|
471
|
-
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed.
|
472
|
-
#
|
473
|
-
# For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.
|
474
|
-
#
|
475
|
-
# The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
|
457
|
+
# An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
|
476
458
|
# @yield [result, response] Access the result along with the Faraday response object
|
477
459
|
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
478
460
|
# @yieldparam response [::Faraday::Response]
|
@@ -534,21 +516,11 @@ module Google
|
|
534
516
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
535
517
|
#
|
536
518
|
# @param filter [::String]
|
537
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
538
|
-
#
|
539
|
-
# For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`.
|
540
|
-
#
|
541
|
-
# You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels.
|
542
|
-
#
|
543
|
-
# To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
519
|
+
# A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:` operator can be used with string fields to match substrings. For non-string fields it is equivalent to the `=` operator. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ```
|
544
520
|
# @param max_results [::Integer]
|
545
521
|
# The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
|
546
522
|
# @param order_by [::String]
|
547
|
-
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name.
|
548
|
-
#
|
549
|
-
# You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first.
|
550
|
-
#
|
551
|
-
# Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
523
|
+
# Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
|
552
524
|
# @param page_token [::String]
|
553
525
|
# Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
|
554
526
|
# @param project [::String]
|