google-cloud-compute-v1 1.0.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/README.md +1 -1
- data/lib/google/cloud/compute/v1/accelerator_types/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/addresses/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/autoscalers/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/backend_buckets/rest/client.rb +78 -1
- 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 +79 -2
- data/lib/google/cloud/compute/v1/backend_services/rest/service_stub.rb +46 -0
- data/lib/google/cloud/compute/v1/compute_pb.rb +534 -2
- data/lib/google/cloud/compute/v1/disk_types/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/disks/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/external_vpn_gateways/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/firewall_policies/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/firewall_policies/rest/service_stub.rb +2 -2
- data/lib/google/cloud/compute/v1/firewalls/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/forwarding_rules/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/global_addresses/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/global_forwarding_rules/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/global_network_endpoint_groups/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/global_operations/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/global_organization_operations/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/global_public_delegated_prefixes/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/health_checks/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/images/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/instance_group_managers/rest/client.rb +5 -5
- data/lib/google/cloud/compute/v1/instance_groups/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/instance_templates/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/instances/rest/client.rb +162 -6
- data/lib/google/cloud/compute/v1/instances/rest/service_stub.rb +91 -0
- data/lib/google/cloud/compute/v1/interconnect_attachments/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/interconnect_locations/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/interconnects/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/licenses/rest/client.rb +1 -1
- 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 +2 -2
- data/lib/google/cloud/compute/v1/network_endpoint_groups/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/networks/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/node_groups/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/node_templates/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/node_types/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/packet_mirrorings/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/projects/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/public_advertised_prefixes/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/public_delegated_prefixes/rest/client.rb +5 -5
- data/lib/google/cloud/compute/v1/region_autoscalers/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_backend_services/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_commitments/rest/client.rb +84 -2
- 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 +1 -1
- data/lib/google/cloud/compute/v1/region_disks/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/region_health_check_services/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_health_checks/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_instance_group_managers/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/region_instance_groups/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/region_network_endpoint_groups/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_notification_endpoints/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/region_operations/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_ssl_certificates/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/region_target_http_proxies/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/region_target_https_proxies/rest/client.rb +5 -5
- data/lib/google/cloud/compute/v1/region_url_maps/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/regions/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/reservations/rest/client.rb +84 -2
- data/lib/google/cloud/compute/v1/reservations/rest/service_stub.rb +48 -0
- data/lib/google/cloud/compute/v1/resource_policies/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/routers/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/routes/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/security_policies/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/service_attachments/rest/client.rb +5 -5
- data/lib/google/cloud/compute/v1/snapshots/rest/client.rb +76 -1
- data/lib/google/cloud/compute/v1/snapshots/rest/service_stub.rb +46 -0
- data/lib/google/cloud/compute/v1/ssl_certificates/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/ssl_policies/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/subnetworks/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/target_grpc_proxies/rest/client.rb +4 -4
- data/lib/google/cloud/compute/v1/target_http_proxies/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/target_https_proxies/rest/client.rb +3 -3
- data/lib/google/cloud/compute/v1/target_instances/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/target_pools/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/target_ssl_proxies/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/target_tcp_proxies/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/target_vpn_gateways/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/url_maps/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/version.rb +1 -1
- data/lib/google/cloud/compute/v1/vpn_gateways/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/vpn_tunnels/rest/client.rb +2 -2
- data/lib/google/cloud/compute/v1/zone_operations/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1/zones/rest/client.rb +1 -1
- data/lib/google/cloud/compute/v1.rb +1 -0
- data/proto_docs/google/cloud/compute/v1/compute.rb +1647 -330
- metadata +8 -3
@@ -176,7 +176,7 @@ module Google
|
|
176
176
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
177
177
|
#
|
178
178
|
# @param filter [::String]
|
179
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
179
|
+
# 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) ```
|
180
180
|
# @param include_all_scopes [::Boolean]
|
181
181
|
# 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.
|
182
182
|
# @param max_results [::Integer]
|
@@ -254,7 +254,7 @@ module Google
|
|
254
254
|
# @param region [::String]
|
255
255
|
# Name of the region of this request.
|
256
256
|
# @param request_id [::String]
|
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).
|
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).
|
258
258
|
# @param service_attachment [::String]
|
259
259
|
# Name of the ServiceAttachment resource to delete.
|
260
260
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -454,7 +454,7 @@ module Google
|
|
454
454
|
# @param region [::String]
|
455
455
|
# Name of the region of this request.
|
456
456
|
# @param request_id [::String]
|
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).
|
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).
|
458
458
|
# @param service_attachment_resource [::Google::Cloud::Compute::V1::ServiceAttachment, ::Hash]
|
459
459
|
# The body resource for this request
|
460
460
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -518,7 +518,7 @@ module Google
|
|
518
518
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
519
519
|
#
|
520
520
|
# @param filter [::String]
|
521
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
521
|
+
# 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) ```
|
522
522
|
# @param max_results [::Integer]
|
523
523
|
# 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`)
|
524
524
|
# @param order_by [::String]
|
@@ -596,7 +596,7 @@ module Google
|
|
596
596
|
# @param region [::String]
|
597
597
|
# The region scoping this request and should conform to RFC1035.
|
598
598
|
# @param request_id [::String]
|
599
|
-
# 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).
|
599
|
+
# 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).
|
600
600
|
# @param service_attachment [::String]
|
601
601
|
# The resource id of the ServiceAttachment to patch. It should conform to RFC1035 resource name or be a string form on an unsigned long number.
|
602
602
|
# @param service_attachment_resource [::Google::Cloud::Compute::V1::ServiceAttachment, ::Hash]
|
@@ -76,6 +76,8 @@ module Google
|
|
76
76
|
initial_delay: 0.1, max_delay: 60.0, multiplier: 1.3, retry_codes: [4, 14]
|
77
77
|
}
|
78
78
|
|
79
|
+
default_config.rpcs.insert.timeout = 600.0
|
80
|
+
|
79
81
|
default_config.rpcs.list.timeout = 600.0
|
80
82
|
default_config.rpcs.list.retry_policy = {
|
81
83
|
initial_delay: 0.1, max_delay: 60.0, multiplier: 1.3, retry_codes: [4, 14]
|
@@ -342,6 +344,72 @@ module Google
|
|
342
344
|
raise ::Google::Cloud::Error.from_error(gapic_error)
|
343
345
|
end
|
344
346
|
|
347
|
+
##
|
348
|
+
# Creates a snapshot in the specified project using the data included in the request. For regular snapshot creation, consider using this method instead of disks.createSnapshot, as this method supports more features, such as creating snapshots in a project different from the source disk project.
|
349
|
+
#
|
350
|
+
# @overload insert(request, options = nil)
|
351
|
+
# Pass arguments to `insert` via a request object, either of type
|
352
|
+
# {::Google::Cloud::Compute::V1::InsertSnapshotRequest} or an equivalent Hash.
|
353
|
+
#
|
354
|
+
# @param request [::Google::Cloud::Compute::V1::InsertSnapshotRequest, ::Hash]
|
355
|
+
# A request object representing the call parameters. Required. To specify no
|
356
|
+
# parameters, or to keep all the default parameter values, pass an empty Hash.
|
357
|
+
# @param options [::Gapic::CallOptions, ::Hash]
|
358
|
+
# Overrides the default settings for this call, e.g, timeout, retries etc. Optional.
|
359
|
+
# Note: currently retry functionality is not implemented. While it is possible
|
360
|
+
# to set it using ::Gapic::CallOptions, it will not be applied
|
361
|
+
#
|
362
|
+
# @overload insert(project: nil, request_id: nil, snapshot_resource: nil)
|
363
|
+
# Pass arguments to `insert` via keyword arguments. Note that at
|
364
|
+
# least one keyword argument is required. To specify no parameters, or to keep all
|
365
|
+
# the default parameter values, pass an empty Hash as a request object (see above).
|
366
|
+
#
|
367
|
+
# @param project [::String]
|
368
|
+
# Project ID for this request.
|
369
|
+
# @param request_id [::String]
|
370
|
+
# 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).
|
371
|
+
# @param snapshot_resource [::Google::Cloud::Compute::V1::Snapshot, ::Hash]
|
372
|
+
# The body resource for this request
|
373
|
+
# @yield [result, response] Access the result along with the Faraday response object
|
374
|
+
# @yieldparam result [::Gapic::Rest::BaseOperation]
|
375
|
+
# @yieldparam response [::Faraday::Response]
|
376
|
+
#
|
377
|
+
# @return [::Gapic::Rest::BaseOperation]
|
378
|
+
#
|
379
|
+
# @raise [::Google::Cloud::Error] if the REST call is aborted.
|
380
|
+
def insert request, options = nil
|
381
|
+
raise ::ArgumentError, "request must be provided" if request.nil?
|
382
|
+
|
383
|
+
request = ::Gapic::Protobuf.coerce request, to: ::Google::Cloud::Compute::V1::InsertSnapshotRequest
|
384
|
+
|
385
|
+
# Converts hash and nil to an options object
|
386
|
+
options = ::Gapic::CallOptions.new(**options.to_h) if options.respond_to? :to_h
|
387
|
+
|
388
|
+
# Customize the options with defaults
|
389
|
+
call_metadata = @config.rpcs.insert.metadata.to_h
|
390
|
+
|
391
|
+
# Set x-goog-api-client header
|
392
|
+
call_metadata[:"x-goog-api-client"] ||= ::Gapic::Headers.x_goog_api_client \
|
393
|
+
lib_name: @config.lib_name, lib_version: @config.lib_version,
|
394
|
+
gapic_version: ::Google::Cloud::Compute::V1::VERSION,
|
395
|
+
transports_version_send: [:rest]
|
396
|
+
|
397
|
+
options.apply_defaults timeout: @config.rpcs.insert.timeout,
|
398
|
+
metadata: call_metadata
|
399
|
+
|
400
|
+
options.apply_defaults timeout: @config.timeout,
|
401
|
+
metadata: @config.metadata
|
402
|
+
|
403
|
+
@snapshots_stub.insert request, options do |result, response|
|
404
|
+
result = ::Gapic::Rest::BaseOperation.new result
|
405
|
+
yield result, response if block_given?
|
406
|
+
return result
|
407
|
+
end
|
408
|
+
rescue ::Faraday::Error => e
|
409
|
+
gapic_error = ::Gapic::Rest::Error.wrap_faraday_error e
|
410
|
+
raise ::Google::Cloud::Error.from_error(gapic_error)
|
411
|
+
end
|
412
|
+
|
345
413
|
##
|
346
414
|
# Retrieves the list of Snapshot resources contained within the specified project.
|
347
415
|
#
|
@@ -363,7 +431,7 @@ module Google
|
|
363
431
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
364
432
|
#
|
365
433
|
# @param filter [::String]
|
366
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
434
|
+
# 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) ```
|
367
435
|
# @param max_results [::Integer]
|
368
436
|
# 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`)
|
369
437
|
# @param order_by [::String]
|
@@ -725,6 +793,11 @@ module Google
|
|
725
793
|
#
|
726
794
|
attr_reader :get_iam_policy
|
727
795
|
##
|
796
|
+
# RPC-specific configuration for `insert`
|
797
|
+
# @return [::Gapic::Config::Method]
|
798
|
+
#
|
799
|
+
attr_reader :insert
|
800
|
+
##
|
728
801
|
# RPC-specific configuration for `list`
|
729
802
|
# @return [::Gapic::Config::Method]
|
730
803
|
#
|
@@ -753,6 +826,8 @@ module Google
|
|
753
826
|
@get = ::Gapic::Config::Method.new get_config
|
754
827
|
get_iam_policy_config = parent_rpcs.get_iam_policy if parent_rpcs.respond_to? :get_iam_policy
|
755
828
|
@get_iam_policy = ::Gapic::Config::Method.new get_iam_policy_config
|
829
|
+
insert_config = parent_rpcs.insert if parent_rpcs.respond_to? :insert
|
830
|
+
@insert = ::Gapic::Config::Method.new insert_config
|
756
831
|
list_config = parent_rpcs.list if parent_rpcs.respond_to? :list
|
757
832
|
@list = ::Gapic::Config::Method.new list_config
|
758
833
|
set_iam_policy_config = parent_rpcs.set_iam_policy if parent_rpcs.respond_to? :set_iam_policy
|
@@ -171,6 +171,52 @@ module Google
|
|
171
171
|
[uri, body, query_string_params]
|
172
172
|
end
|
173
173
|
|
174
|
+
##
|
175
|
+
# Baseline implementation for the insert REST call
|
176
|
+
#
|
177
|
+
# @param request_pb [::Google::Cloud::Compute::V1::InsertSnapshotRequest]
|
178
|
+
# A request object representing the call parameters. Required.
|
179
|
+
# @param options [::Gapic::CallOptions]
|
180
|
+
# Overrides the default settings for this call, e.g, timeout, retries etc. Optional.
|
181
|
+
#
|
182
|
+
# @yield [result, response] Access the result along with the Faraday response object
|
183
|
+
# @yieldparam result [::Google::Cloud::Compute::V1::Operation]
|
184
|
+
# @yieldparam response [::Faraday::Response]
|
185
|
+
#
|
186
|
+
# @return [::Google::Cloud::Compute::V1::Operation]
|
187
|
+
# A result object deserialized from the server's reply
|
188
|
+
def insert request_pb, options = nil
|
189
|
+
raise ::ArgumentError, "request must be provided" if request_pb.nil?
|
190
|
+
|
191
|
+
uri, body, query_string_params = transcode_insert_request request_pb
|
192
|
+
response = @client_stub.make_post_request(
|
193
|
+
uri: uri,
|
194
|
+
body: body,
|
195
|
+
params: query_string_params,
|
196
|
+
options: options
|
197
|
+
)
|
198
|
+
result = ::Google::Cloud::Compute::V1::Operation.decode_json response.body, ignore_unknown_fields: true
|
199
|
+
|
200
|
+
yield result, response if block_given?
|
201
|
+
result
|
202
|
+
end
|
203
|
+
|
204
|
+
##
|
205
|
+
# GRPC transcoding helper method for the insert REST call
|
206
|
+
#
|
207
|
+
# @param request_pb [::Google::Cloud::Compute::V1::InsertSnapshotRequest]
|
208
|
+
# A request object representing the call parameters. Required.
|
209
|
+
# @return [Array(String, [String, nil], Hash{String => String})]
|
210
|
+
# Uri, Body, Query string parameters
|
211
|
+
def transcode_insert_request request_pb
|
212
|
+
uri = "/compute/v1/projects/#{request_pb.project}/global/snapshots"
|
213
|
+
body = request_pb.snapshot_resource.to_json
|
214
|
+
query_string_params = {}
|
215
|
+
query_string_params["requestId"] = request_pb.request_id.to_s if request_pb.has_request_id?
|
216
|
+
|
217
|
+
[uri, body, query_string_params]
|
218
|
+
end
|
219
|
+
|
174
220
|
##
|
175
221
|
# Baseline implementation for the list REST call
|
176
222
|
#
|
@@ -165,7 +165,7 @@ module Google
|
|
165
165
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
166
166
|
#
|
167
167
|
# @param filter [::String]
|
168
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
168
|
+
# 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) ```
|
169
169
|
# @param include_all_scopes [::Boolean]
|
170
170
|
# 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.
|
171
171
|
# @param max_results [::Integer]
|
@@ -241,7 +241,7 @@ module Google
|
|
241
241
|
# @param project [::String]
|
242
242
|
# Project ID for this request.
|
243
243
|
# @param request_id [::String]
|
244
|
-
# 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).
|
244
|
+
# 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).
|
245
245
|
# @param ssl_certificate [::String]
|
246
246
|
# Name of the SslCertificate resource to delete.
|
247
247
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -370,7 +370,7 @@ module Google
|
|
370
370
|
# @param project [::String]
|
371
371
|
# Project ID for this request.
|
372
372
|
# @param request_id [::String]
|
373
|
-
# 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).
|
373
|
+
# 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).
|
374
374
|
# @param ssl_certificate_resource [::Google::Cloud::Compute::V1::SslCertificate, ::Hash]
|
375
375
|
# The body resource for this request
|
376
376
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -434,7 +434,7 @@ module Google
|
|
434
434
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
435
435
|
#
|
436
436
|
# @param filter [::String]
|
437
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
437
|
+
# 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) ```
|
438
438
|
# @param max_results [::Integer]
|
439
439
|
# 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`)
|
440
440
|
# @param order_by [::String]
|
@@ -362,7 +362,7 @@ module Google
|
|
362
362
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
363
363
|
#
|
364
364
|
# @param filter [::String]
|
365
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
365
|
+
# 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) ```
|
366
366
|
# @param max_results [::Integer]
|
367
367
|
# 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`)
|
368
368
|
# @param order_by [::String]
|
@@ -434,7 +434,7 @@ module Google
|
|
434
434
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
435
435
|
#
|
436
436
|
# @param filter [::String]
|
437
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
437
|
+
# 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) ```
|
438
438
|
# @param max_results [::Integer]
|
439
439
|
# 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`)
|
440
440
|
# @param order_by [::String]
|
@@ -185,7 +185,7 @@ module Google
|
|
185
185
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
186
186
|
#
|
187
187
|
# @param filter [::String]
|
188
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
188
|
+
# 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) ```
|
189
189
|
# @param include_all_scopes [::Boolean]
|
190
190
|
# 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.
|
191
191
|
# @param max_results [::Integer]
|
@@ -597,7 +597,7 @@ module Google
|
|
597
597
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
598
598
|
#
|
599
599
|
# @param filter [::String]
|
600
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
600
|
+
# 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) ```
|
601
601
|
# @param max_results [::Integer]
|
602
602
|
# 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`)
|
603
603
|
# @param order_by [::String]
|
@@ -671,7 +671,7 @@ module Google
|
|
671
671
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
672
672
|
#
|
673
673
|
# @param filter [::String]
|
674
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
674
|
+
# 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) ```
|
675
675
|
# @param max_results [::Integer]
|
676
676
|
# 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`)
|
677
677
|
# @param order_by [::String]
|
@@ -164,7 +164,7 @@ module Google
|
|
164
164
|
# @param project [::String]
|
165
165
|
# Project ID for this request.
|
166
166
|
# @param request_id [::String]
|
167
|
-
# 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).
|
167
|
+
# 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).
|
168
168
|
# @param target_grpc_proxy [::String]
|
169
169
|
# Name of the TargetGrpcProxy resource to delete.
|
170
170
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -293,7 +293,7 @@ module Google
|
|
293
293
|
# @param project [::String]
|
294
294
|
# Project ID for this request.
|
295
295
|
# @param request_id [::String]
|
296
|
-
# 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).
|
296
|
+
# 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).
|
297
297
|
# @param target_grpc_proxy_resource [::Google::Cloud::Compute::V1::TargetGrpcProxy, ::Hash]
|
298
298
|
# The body resource for this request
|
299
299
|
# @yield [result, response] Access the result along with the Faraday response object
|
@@ -357,7 +357,7 @@ module Google
|
|
357
357
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
358
358
|
#
|
359
359
|
# @param filter [::String]
|
360
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
360
|
+
# 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) ```
|
361
361
|
# @param max_results [::Integer]
|
362
362
|
# 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`)
|
363
363
|
# @param order_by [::String]
|
@@ -431,7 +431,7 @@ module Google
|
|
431
431
|
# @param project [::String]
|
432
432
|
# Project ID for this request.
|
433
433
|
# @param request_id [::String]
|
434
|
-
# 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).
|
434
|
+
# 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).
|
435
435
|
# @param target_grpc_proxy [::String]
|
436
436
|
# Name of the TargetGrpcProxy resource to patch.
|
437
437
|
# @param target_grpc_proxy_resource [::Google::Cloud::Compute::V1::TargetGrpcProxy, ::Hash]
|
@@ -169,7 +169,7 @@ module Google
|
|
169
169
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
170
170
|
#
|
171
171
|
# @param filter [::String]
|
172
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
172
|
+
# 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) ```
|
173
173
|
# @param include_all_scopes [::Boolean]
|
174
174
|
# 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.
|
175
175
|
# @param max_results [::Integer]
|
@@ -438,7 +438,7 @@ module Google
|
|
438
438
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
439
439
|
#
|
440
440
|
# @param filter [::String]
|
441
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
441
|
+
# 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) ```
|
442
442
|
# @param max_results [::Integer]
|
443
443
|
# 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`)
|
444
444
|
# @param order_by [::String]
|
@@ -512,7 +512,7 @@ module Google
|
|
512
512
|
# @param project [::String]
|
513
513
|
# Project ID for this request.
|
514
514
|
# @param request_id [::String]
|
515
|
-
# 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).
|
515
|
+
# 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).
|
516
516
|
# @param target_http_proxy [::String]
|
517
517
|
# Name of the TargetHttpProxy resource to patch.
|
518
518
|
# @param target_http_proxy_resource [::Google::Cloud::Compute::V1::TargetHttpProxy, ::Hash]
|
@@ -175,7 +175,7 @@ module Google
|
|
175
175
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
176
176
|
#
|
177
177
|
# @param filter [::String]
|
178
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
178
|
+
# 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) ```
|
179
179
|
# @param include_all_scopes [::Boolean]
|
180
180
|
# 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.
|
181
181
|
# @param max_results [::Integer]
|
@@ -444,7 +444,7 @@ module Google
|
|
444
444
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
445
445
|
#
|
446
446
|
# @param filter [::String]
|
447
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
447
|
+
# 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) ```
|
448
448
|
# @param max_results [::Integer]
|
449
449
|
# 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`)
|
450
450
|
# @param order_by [::String]
|
@@ -518,7 +518,7 @@ module Google
|
|
518
518
|
# @param project [::String]
|
519
519
|
# Project ID for this request.
|
520
520
|
# @param request_id [::String]
|
521
|
-
# 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).
|
521
|
+
# 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).
|
522
522
|
# @param target_https_proxy [::String]
|
523
523
|
# Name of the TargetHttpsProxy resource to patch.
|
524
524
|
# @param target_https_proxy_resource [::Google::Cloud::Compute::V1::TargetHttpsProxy, ::Hash]
|
@@ -165,7 +165,7 @@ module Google
|
|
165
165
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
166
166
|
#
|
167
167
|
# @param filter [::String]
|
168
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
168
|
+
# 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) ```
|
169
169
|
# @param include_all_scopes [::Boolean]
|
170
170
|
# 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.
|
171
171
|
# @param max_results [::Integer]
|
@@ -440,7 +440,7 @@ module Google
|
|
440
440
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
441
441
|
#
|
442
442
|
# @param filter [::String]
|
443
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
443
|
+
# 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) ```
|
444
444
|
# @param max_results [::Integer]
|
445
445
|
# 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`)
|
446
446
|
# @param order_by [::String]
|
@@ -317,7 +317,7 @@ module Google
|
|
317
317
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
318
318
|
#
|
319
319
|
# @param filter [::String]
|
320
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
320
|
+
# 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) ```
|
321
321
|
# @param include_all_scopes [::Boolean]
|
322
322
|
# 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.
|
323
323
|
# @param max_results [::Integer]
|
@@ -659,7 +659,7 @@ module Google
|
|
659
659
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
660
660
|
#
|
661
661
|
# @param filter [::String]
|
662
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
662
|
+
# 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) ```
|
663
663
|
# @param max_results [::Integer]
|
664
664
|
# 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`)
|
665
665
|
# @param order_by [::String]
|
@@ -363,7 +363,7 @@ module Google
|
|
363
363
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
364
364
|
#
|
365
365
|
# @param filter [::String]
|
366
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
366
|
+
# 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) ```
|
367
367
|
# @param max_results [::Integer]
|
368
368
|
# 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`)
|
369
369
|
# @param order_by [::String]
|
@@ -359,7 +359,7 @@ module Google
|
|
359
359
|
# the default parameter values, pass an empty Hash as a request object (see above).
|
360
360
|
#
|
361
361
|
# @param filter [::String]
|
362
|
-
# A filter expression that filters resources listed in the response. The expression must specify the field name,
|
362
|
+
# 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) ```
|
363
363
|
# @param max_results [::Integer]
|
364
364
|
# 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`)
|
365
365
|
# @param order_by [::String]
|