diff --git a/api_names_out.yaml b/api_names_out.yaml index 7f594b7a0..9a30cca49 100644 --- a/api_names_out.yaml +++ b/api_names_out.yaml @@ -16523,6 +16523,7 @@ "/compute:alpha/Commitment/startTimestamp": start_timestamp "/compute:alpha/Commitment/status": status "/compute:alpha/Commitment/statusMessage": status_message +"/compute:alpha/Commitment/type": type "/compute:alpha/CommitmentAggregatedList": commitment_aggregated_list "/compute:alpha/CommitmentAggregatedList/id": id "/compute:alpha/CommitmentAggregatedList/items": items @@ -21039,6 +21040,7 @@ "/compute:alpha/compute.securityPolicies.insert": insert_security_policy "/compute:alpha/compute.securityPolicies.insert/project": project "/compute:alpha/compute.securityPolicies.insert/requestId": request_id +"/compute:alpha/compute.securityPolicies.insert/validateOnly": validate_only "/compute:alpha/compute.securityPolicies.list": list_security_policies "/compute:alpha/compute.securityPolicies.list/filter": filter "/compute:alpha/compute.securityPolicies.list/maxResults": max_results @@ -22131,6 +22133,7 @@ "/compute:beta/Firewall/destinationRanges": destination_ranges "/compute:beta/Firewall/destinationRanges/destination_range": destination_range "/compute:beta/Firewall/direction": direction +"/compute:beta/Firewall/disabled": disabled "/compute:beta/Firewall/id": id "/compute:beta/Firewall/kind": kind "/compute:beta/Firewall/name": name @@ -22776,14 +22779,17 @@ "/compute:beta/Interconnect/provisionedLinkCount": provisioned_link_count "/compute:beta/Interconnect/requestedLinkCount": requested_link_count "/compute:beta/Interconnect/selfLink": self_link +"/compute:beta/Interconnect/state": state "/compute:beta/InterconnectAttachment": interconnect_attachment "/compute:beta/InterconnectAttachment/adminEnabled": admin_enabled +"/compute:beta/InterconnectAttachment/bandwidth": bandwidth "/compute:beta/InterconnectAttachment/candidateSubnets": candidate_subnets "/compute:beta/InterconnectAttachment/candidateSubnets/candidate_subnet": candidate_subnet "/compute:beta/InterconnectAttachment/cloudRouterIpAddress": cloud_router_ip_address "/compute:beta/InterconnectAttachment/creationTimestamp": creation_timestamp "/compute:beta/InterconnectAttachment/customerRouterIpAddress": customer_router_ip_address "/compute:beta/InterconnectAttachment/description": description +"/compute:beta/InterconnectAttachment/edgeAvailabilityDomain": edge_availability_domain "/compute:beta/InterconnectAttachment/googleReferenceId": google_reference_id "/compute:beta/InterconnectAttachment/id": id "/compute:beta/InterconnectAttachment/interconnect": interconnect @@ -22793,10 +22799,14 @@ "/compute:beta/InterconnectAttachment/labels/label": label "/compute:beta/InterconnectAttachment/name": name "/compute:beta/InterconnectAttachment/operationalStatus": operational_status +"/compute:beta/InterconnectAttachment/pairingKey": pairing_key +"/compute:beta/InterconnectAttachment/partnerAsn": partner_asn +"/compute:beta/InterconnectAttachment/partnerMetadata": partner_metadata "/compute:beta/InterconnectAttachment/privateInterconnectInfo": private_interconnect_info "/compute:beta/InterconnectAttachment/region": region "/compute:beta/InterconnectAttachment/router": router "/compute:beta/InterconnectAttachment/selfLink": self_link +"/compute:beta/InterconnectAttachment/state": state "/compute:beta/InterconnectAttachment/type": type "/compute:beta/InterconnectAttachment/vlanTag8021q": vlan_tag8021q "/compute:beta/InterconnectAttachmentAggregatedList": interconnect_attachment_aggregated_list @@ -22827,6 +22837,10 @@ "/compute:beta/InterconnectAttachmentList/warning/data/datum/key": key "/compute:beta/InterconnectAttachmentList/warning/data/datum/value": value "/compute:beta/InterconnectAttachmentList/warning/message": message +"/compute:beta/InterconnectAttachmentPartnerMetadata": interconnect_attachment_partner_metadata +"/compute:beta/InterconnectAttachmentPartnerMetadata/interconnectName": interconnect_name +"/compute:beta/InterconnectAttachmentPartnerMetadata/partnerName": partner_name +"/compute:beta/InterconnectAttachmentPartnerMetadata/portalUrl": portal_url "/compute:beta/InterconnectAttachmentPrivateInfo": interconnect_attachment_private_info "/compute:beta/InterconnectAttachmentPrivateInfo/tag8021q": tag8021q "/compute:beta/InterconnectAttachmentsScopedList": interconnect_attachments_scoped_list @@ -23690,6 +23704,7 @@ "/compute:beta/Subnetwork/allowSubnetCidrRoutesOverlap": allow_subnet_cidr_routes_overlap "/compute:beta/Subnetwork/creationTimestamp": creation_timestamp "/compute:beta/Subnetwork/description": description +"/compute:beta/Subnetwork/enableFlowLogs": enable_flow_logs "/compute:beta/Subnetwork/fingerprint": fingerprint "/compute:beta/Subnetwork/gatewayAddress": gateway_address "/compute:beta/Subnetwork/id": id @@ -25003,6 +25018,10 @@ "/compute:beta/compute.instances.setTags/project": project "/compute:beta/compute.instances.setTags/requestId": request_id "/compute:beta/compute.instances.setTags/zone": zone +"/compute:beta/compute.instances.simulateMaintenanceEvent": simulate_instance_maintenance_event +"/compute:beta/compute.instances.simulateMaintenanceEvent/instance": instance +"/compute:beta/compute.instances.simulateMaintenanceEvent/project": project +"/compute:beta/compute.instances.simulateMaintenanceEvent/zone": zone "/compute:beta/compute.instances.start": start_instance "/compute:beta/compute.instances.start/instance": instance "/compute:beta/compute.instances.start/project": project @@ -30384,6 +30403,7 @@ "/container:v1beta1/Cluster/maintenancePolicy": maintenance_policy "/container:v1beta1/Cluster/masterAuth": master_auth "/container:v1beta1/Cluster/masterAuthorizedNetworksConfig": master_authorized_networks_config +"/container:v1beta1/Cluster/masterIpv4CidrBlock": master_ipv4_cidr_block "/container:v1beta1/Cluster/monitoringService": monitoring_service "/container:v1beta1/Cluster/name": name "/container:v1beta1/Cluster/network": network @@ -30393,6 +30413,7 @@ "/container:v1beta1/Cluster/nodePools": node_pools "/container:v1beta1/Cluster/nodePools/node_pool": node_pool "/container:v1beta1/Cluster/podSecurityPolicyConfig": pod_security_policy_config +"/container:v1beta1/Cluster/privateCluster": private_cluster "/container:v1beta1/Cluster/resourceLabels": resource_labels "/container:v1beta1/Cluster/resourceLabels/resource_label": resource_label "/container:v1beta1/Cluster/selfLink": self_link @@ -36033,6 +36054,7 @@ "/deploymentmanager:v2/deploymentmanager.deployments.getIamPolicy/project": project "/deploymentmanager:v2/deploymentmanager.deployments.getIamPolicy/resource": resource "/deploymentmanager:v2/deploymentmanager.deployments.insert": insert_deployment +"/deploymentmanager:v2/deploymentmanager.deployments.insert/createPolicy": create_policy "/deploymentmanager:v2/deploymentmanager.deployments.insert/preview": preview "/deploymentmanager:v2/deploymentmanager.deployments.insert/project": project "/deploymentmanager:v2/deploymentmanager.deployments.list": list_deployments diff --git a/generated/google/apis/cloudresourcemanager_v1.rb b/generated/google/apis/cloudresourcemanager_v1.rb index d306e22cc..f07f9c9e2 100644 --- a/generated/google/apis/cloudresourcemanager_v1.rb +++ b/generated/google/apis/cloudresourcemanager_v1.rb @@ -26,7 +26,7 @@ module Google # @see https://cloud.google.com/resource-manager module CloudresourcemanagerV1 VERSION = 'V1' - REVISION = '20180312' + REVISION = '20180315' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudresourcemanager_v1/service.rb b/generated/google/apis/cloudresourcemanager_v1/service.rb index 88bb34343..649d97511 100644 --- a/generated/google/apis/cloudresourcemanager_v1/service.rb +++ b/generated/google/apis/cloudresourcemanager_v1/service.rb @@ -854,9 +854,7 @@ module Google # Marks the Project identified by the specified # `project_id` (for example, `my-project-123`) for deletion. - # This method will only affect the Project if the following criteria are met: - # + The Project does not have a billing account associated with it. - # + The Project has a lifecycle state of + # This method will only affect the Project if it has a lifecycle state of # ACTIVE. # This method changes the Project's lifecycle state from # ACTIVE diff --git a/generated/google/apis/cloudresourcemanager_v1beta1.rb b/generated/google/apis/cloudresourcemanager_v1beta1.rb index 650f54518..3f2e3281d 100644 --- a/generated/google/apis/cloudresourcemanager_v1beta1.rb +++ b/generated/google/apis/cloudresourcemanager_v1beta1.rb @@ -26,7 +26,7 @@ module Google # @see https://cloud.google.com/resource-manager module CloudresourcemanagerV1beta1 VERSION = 'V1beta1' - REVISION = '20180312' + REVISION = '20180315' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudresourcemanager_v1beta1/service.rb b/generated/google/apis/cloudresourcemanager_v1beta1/service.rb index 0019a1279..0ffd53913 100644 --- a/generated/google/apis/cloudresourcemanager_v1beta1/service.rb +++ b/generated/google/apis/cloudresourcemanager_v1beta1/service.rb @@ -317,9 +317,7 @@ module Google # Marks the Project identified by the specified # `project_id` (for example, `my-project-123`) for deletion. - # This method will only affect the Project if the following criteria are met: - # + The Project does not have a billing account associated with it. - # + The Project has a lifecycle state of + # This method will only affect the Project if it has a lifecycle state of # ACTIVE. # This method changes the Project's lifecycle state from # ACTIVE diff --git a/generated/google/apis/cloudtrace_v1.rb b/generated/google/apis/cloudtrace_v1.rb index 5d8f4d881..d3b41cc87 100644 --- a/generated/google/apis/cloudtrace_v1.rb +++ b/generated/google/apis/cloudtrace_v1.rb @@ -27,7 +27,7 @@ module Google # @see https://cloud.google.com/trace module CloudtraceV1 VERSION = 'V1' - REVISION = '20171106' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudtrace_v1/classes.rb b/generated/google/apis/cloudtrace_v1/classes.rb index fdf86f480..b2b2ae744 100644 --- a/generated/google/apis/cloudtrace_v1/classes.rb +++ b/generated/google/apis/cloudtrace_v1/classes.rb @@ -142,9 +142,11 @@ module Google # * `/http/client_region` # * `/http/host` # * `/http/method` + # * `/http/path` # * `/http/redirected_url` # * `/http/request/size` # * `/http/response/size` + # * `/http/route` # * `/http/status_code` # * `/http/url` # * `/http/user_agent` diff --git a/generated/google/apis/compute_alpha.rb b/generated/google/apis/compute_alpha.rb index 483e8da59..4349b07eb 100644 --- a/generated/google/apis/compute_alpha.rb +++ b/generated/google/apis/compute_alpha.rb @@ -25,7 +25,7 @@ module Google # @see https://developers.google.com/compute/docs/reference/latest/ module ComputeAlpha VERSION = 'Alpha' - REVISION = '20180220' + REVISION = '20180314' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/compute_alpha/classes.rb b/generated/google/apis/compute_alpha/classes.rb index e1272bd2b..5ff9af095 100644 --- a/generated/google/apis/compute_alpha/classes.rb +++ b/generated/google/apis/compute_alpha/classes.rb @@ -3448,6 +3448,13 @@ module Google # @return [String] attr_accessor :status_message + # The type of commitment, which affects the discount rate and the eligible + # resources. Type LARGE_VM specifies a commitment that will only apply to large + # VMs. Type NORMAL specifies a commitment that applies to all other resources. + # Corresponds to the JSON property `type` + # @return [String] + attr_accessor :type + def initialize(**args) update!(**args) end @@ -3467,6 +3474,7 @@ module Google @start_timestamp = args[:start_timestamp] if args.key?(:start_timestamp) @status = args[:status] if args.key?(:status) @status_message = args[:status_message] if args.key?(:status_message) + @type = args[:type] if args.key?(:type) end end @@ -11996,12 +12004,14 @@ module Google attr_accessor :admin_enabled alias_method :admin_enabled?, :admin_enabled - # + # [Deprecated] Replaced by edge_availability_domain. # Corresponds to the JSON property `availabilityZone` # @return [String] attr_accessor :availability_zone - # + # Provisioned bandwidth capacity for the interconnectAttachment. Can be set by + # the partner to update the customer's provisioned bandwidth. Output only for + # for PARTNER type, mutable for PARTNER_PROVIDER, not available for DEDICATED. # Corresponds to the JSON property `bandwidth` # @return [String] attr_accessor :bandwidth @@ -12039,13 +12049,12 @@ module Google # @return [String] attr_accessor :description - # Desired availability domain for the attachment. Can only be specified when - # creating PARTNER-type InterconnectAttachments. - # For improved reliability, customers should configure a pair of attachments - # with one per availability domain. The selected availability domain will be - # provided to the Partner via the pairing key so that the provisioned circuit - # will lie in the specified domain. If not specified, the value will default to - # AVAILABILITY_DOMAIN_ANY. + # Desired availability domain for the attachment. Only available for type + # PARTNER, at creation time. For improved reliability, customers should + # configure a pair of attachments with one per availability domain. The selected + # availability domain will be provided to the Partner via the pairing key so + # that the provisioned circuit will lie in the specified domain. If not + # specified, the value will default to AVAILABILITY_DOMAIN_ANY. # Corresponds to the JSON property `edgeAvailabilityDomain` # @return [String] attr_accessor :edge_availability_domain @@ -12110,23 +12119,23 @@ module Google attr_accessor :operational_status # [Output only for type PARTNER. Input only for PARTNER_PROVIDER. Not present - # for DEDICATED]. Opaque string identifying an PARTNER attachment. Of the form ? - # cloud-region/XXXXXX?. + # for DEDICATED]. The opaque identifier of an PARTNER attachment used to + # initiate provisioning with a selected partner. Of the form "XXXXX/region/ + # domain" # Corresponds to the JSON property `pairingKey` # @return [String] attr_accessor :pairing_key - # [Output only for PARTNER. Input for PARTNER_PROVIDER. Not present for - # DEDICATED] BGP ASN of the Partner. A layer 3 Partner should supply this if - # they configured BGP on behalf of the customer. + # Optional BGP ASN for the router that should be supplied by a layer 3 Partner + # if they configured BGP on behalf of the customer. Output only for PARTNER type, + # input only for PARTNER_PROVIDER, not available for DEDICATED. # Corresponds to the JSON property `partnerAsn` # @return [Fixnum] attr_accessor :partner_asn # Informational metadata about Partner attachments from Partners to display to # customers. These fields are propagated from PARTNER_PROVIDER attachments to - # their corresponding PARTNER attachments. Only mutable for PARTNER_PROVIDER - # type, output-only for PARTNER, not available for DEDICATED. + # their corresponding PARTNER attachments. # Corresponds to the JSON property `partnerMetadata` # @return [Google::Apis::ComputeAlpha::InterconnectAttachmentPartnerMetadata] attr_accessor :partner_metadata @@ -12157,8 +12166,7 @@ module Google # @return [String] attr_accessor :self_link - # [Output Only] The current state of whether or not this interconnect attachment - # is functional. + # [Output Only] The current state of this attachment's functionality. # Corresponds to the JSON property `state` # @return [String] attr_accessor :state @@ -12450,8 +12458,7 @@ module Google # Informational metadata about Partner attachments from Partners to display to # customers. These fields are propagated from PARTNER_PROVIDER attachments to - # their corresponding PARTNER attachments. Only mutable for PARTNER_PROVIDER - # type, output-only for PARTNER, not available for DEDICATED. + # their corresponding PARTNER attachments. class InterconnectAttachmentPartnerMetadata include Google::Apis::Core::Hashable diff --git a/generated/google/apis/compute_alpha/representations.rb b/generated/google/apis/compute_alpha/representations.rb index a70091983..de2f8c2c1 100644 --- a/generated/google/apis/compute_alpha/representations.rb +++ b/generated/google/apis/compute_alpha/representations.rb @@ -4418,6 +4418,7 @@ module Google property :start_timestamp, as: 'startTimestamp' property :status, as: 'status' property :status_message, as: 'statusMessage' + property :type, as: 'type' end end diff --git a/generated/google/apis/compute_alpha/service.rb b/generated/google/apis/compute_alpha/service.rb index d38ce69a6..6001b429a 100644 --- a/generated/google/apis/compute_alpha/service.rb +++ b/generated/google/apis/compute_alpha/service.rb @@ -57,25 +57,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -177,25 +174,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -254,25 +248,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -480,25 +471,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -658,25 +646,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -885,25 +870,22 @@ module Google # @param [String] zone # Name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1409,25 +1391,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1732,25 +1711,22 @@ module Google # @param [String] project # Name of the project scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2045,25 +2021,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2370,25 +2343,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2490,25 +2460,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2567,25 +2534,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2901,25 +2865,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3320,25 +3281,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3547,25 +3505,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3774,25 +3729,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4207,25 +4159,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4507,25 +4456,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4775,25 +4721,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4926,25 +4869,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5142,25 +5082,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5368,25 +5305,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5488,25 +5422,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5565,25 +5496,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5834,25 +5762,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6141,25 +6066,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6508,25 +6430,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7013,25 +6932,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7281,25 +7197,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7674,25 +7587,22 @@ module Google # @param [String] zone # The name of the zone where the managed instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7809,25 +7719,22 @@ module Google # @param [String] instance_group_manager # The name of the managed instance group. It should conform to RFC1035. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8542,25 +8449,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8772,25 +8676,22 @@ module Google # @param [String] zone # The name of the zone where the instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8855,25 +8756,22 @@ module Google # included instances. # @param [Google::Apis::ComputeAlpha::InstanceGroupsListInstancesRequest] instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9240,25 +9138,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9474,25 +9369,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10025,25 +9917,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10108,25 +9997,22 @@ module Google # Name of the target instance scoping this request, or '-' if the request should # span over all instances in the container. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11462,25 +11348,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11731,25 +11614,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12052,25 +11932,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12348,25 +12225,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12946,25 +12820,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13105,25 +12976,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13225,25 +13093,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13302,25 +13167,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13570,25 +13432,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13736,25 +13595,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14088,25 +13944,22 @@ module Google # The name of the zone where the network endpoint group is located. It should # comply with RFC1035. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14172,25 +14025,22 @@ module Google # of included network endpoints. It should comply with RFC1035. # @param [Google::Apis::ComputeAlpha::NetworkEndpointGroupsListEndpointsRequest] network_endpoint_groups_list_endpoints_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14489,25 +14339,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14567,25 +14414,22 @@ module Google # @param [String] network # Name of the network to return. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [String] ip_cidr_range # (Optional) IP CIDR range filter, example: "10.128.10.0/30". # @param [Fixnum] max_results @@ -15933,25 +15777,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16365,25 +16206,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16605,25 +16443,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16779,25 +16614,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16944,25 +16776,22 @@ module Google # @param [String] region # The name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17235,25 +17064,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17846,25 +17672,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17978,25 +17801,22 @@ module Google # @param [String] instance_group_manager # The name of the managed instance group. It should conform to RFC1035. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18612,25 +18432,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18696,25 +18513,22 @@ module Google # Name of the regional instance group for which we want to list the instances. # @param [Google::Apis::ComputeAlpha::RegionInstanceGroupsListInstancesRequest] region_instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18958,25 +18772,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19074,25 +18885,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19150,25 +18958,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19418,25 +19223,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19838,25 +19640,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20140,6 +19939,8 @@ module Google # 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). + # @param [Boolean] validate_only + # If true, the request will not be committed. # @param [String] fields # Selector specifying which fields to include in a partial response. # @param [String] quota_user @@ -20161,7 +19962,7 @@ module Google # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification # @raise [Google::Apis::AuthorizationError] Authorization is required - def insert_security_policy(project, security_policy_object = nil, request_id: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block) + def insert_security_policy(project, security_policy_object = nil, request_id: nil, validate_only: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block) command = make_simple_command(:post, '{project}/global/securityPolicies', options) command.request_representation = Google::Apis::ComputeAlpha::SecurityPolicy::Representation command.request_object = security_policy_object @@ -20169,6 +19970,7 @@ module Google command.response_class = Google::Apis::ComputeAlpha::Operation command.params['project'] = project unless project.nil? command.query['requestId'] = request_id unless request_id.nil? + command.query['validateOnly'] = validate_only unless validate_only.nil? command.query['fields'] = fields unless fields.nil? command.query['quotaUser'] = quota_user unless quota_user.nil? command.query['userIp'] = user_ip unless user_ip.nil? @@ -20179,25 +19981,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20570,25 +20369,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20912,25 +20708,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21171,25 +20964,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21248,25 +21038,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21419,25 +21206,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21744,25 +21528,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21821,25 +21602,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -22244,25 +22022,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -22555,25 +22330,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -22889,25 +22661,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -23117,25 +22886,22 @@ module Google # @param [String] zone # Name of the zone scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -23350,25 +23116,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -23622,25 +23385,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -24055,25 +23815,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -24529,25 +24286,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -24752,25 +24506,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -24980,25 +24731,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -25352,25 +25100,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -25619,25 +25364,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -25847,25 +25589,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -26107,25 +25846,22 @@ module Google # @param [String] zone # Name of the zone for request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -26223,25 +25959,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 diff --git a/generated/google/apis/compute_beta.rb b/generated/google/apis/compute_beta.rb index dee066bea..c4f66bd92 100644 --- a/generated/google/apis/compute_beta.rb +++ b/generated/google/apis/compute_beta.rb @@ -25,7 +25,7 @@ module Google # @see https://developers.google.com/compute/docs/reference/latest/ module ComputeBeta VERSION = 'Beta' - REVISION = '20180220' + REVISION = '20180314' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/compute_beta/classes.rb b/generated/google/apis/compute_beta/classes.rb index 5b44a157c..c2c7d0e44 100644 --- a/generated/google/apis/compute_beta/classes.rb +++ b/generated/google/apis/compute_beta/classes.rb @@ -4874,6 +4874,15 @@ module Google # @return [String] attr_accessor :direction + # Denotes whether the firewall rule is disabled, i.e not applied to the network + # it is associated with. When set to true, the firewall rule is not enforced and + # the network behaves as if it did not exist. If this is unspecified, the + # firewall rule will be enabled. + # Corresponds to the JSON property `disabled` + # @return [Boolean] + attr_accessor :disabled + alias_method :disabled?, :disabled + # [Output Only] The unique identifier for the resource. This identifier is # defined by the server. # Corresponds to the JSON property `id` @@ -4991,6 +5000,7 @@ module Google @description = args[:description] if args.key?(:description) @destination_ranges = args[:destination_ranges] if args.key?(:destination_ranges) @direction = args[:direction] if args.key?(:direction) + @disabled = args[:disabled] if args.key?(:disabled) @id = args[:id] if args.key?(:id) @kind = args[:kind] if args.key?(:kind) @name = args[:name] if args.key?(:name) @@ -10059,6 +10069,12 @@ module Google # @return [String] attr_accessor :self_link + # [Output Only] The current state of whether or not this Interconnect is + # functional. + # Corresponds to the JSON property `state` + # @return [String] + attr_accessor :state + def initialize(**args) update!(**args) end @@ -10088,6 +10104,7 @@ module Google @provisioned_link_count = args[:provisioned_link_count] if args.key?(:provisioned_link_count) @requested_link_count = args[:requested_link_count] if args.key?(:requested_link_count) @self_link = args[:self_link] if args.key?(:self_link) + @state = args[:state] if args.key?(:state) end end @@ -10104,6 +10121,13 @@ module Google attr_accessor :admin_enabled alias_method :admin_enabled?, :admin_enabled + # Provisioned bandwidth capacity for the interconnectAttachment. Can be set by + # the partner to update the customer's provisioned bandwidth. Output only for + # for PARTNER type, mutable for PARTNER_PROVIDER, not available for DEDICATED. + # Corresponds to the JSON property `bandwidth` + # @return [String] + attr_accessor :bandwidth + # Up to 16 candidate prefixes that can be used to restrict the allocation of # cloudRouterIpAddress and customerRouterIpAddress for this attachment. All # prefixes must be within link-local address space (169.254.0.0/16) and must be / @@ -10137,6 +10161,16 @@ module Google # @return [String] attr_accessor :description + # Desired availability domain for the attachment. Only available for type + # PARTNER, at creation time. For improved reliability, customers should + # configure a pair of attachments with one per availability domain. The selected + # availability domain will be provided to the Partner via the pairing key so + # that the provisioned circuit will lie in the specified domain. If not + # specified, the value will default to AVAILABILITY_DOMAIN_ANY. + # Corresponds to the JSON property `edgeAvailabilityDomain` + # @return [String] + attr_accessor :edge_availability_domain + # [Output Only] Google reference ID, to be used when raising support tickets # with Google or otherwise to debug backend connectivity issues. # Corresponds to the JSON property `googleReferenceId` @@ -10196,6 +10230,28 @@ module Google # @return [String] attr_accessor :operational_status + # [Output only for type PARTNER. Input only for PARTNER_PROVIDER. Not present + # for DEDICATED]. The opaque identifier of an PARTNER attachment used to + # initiate provisioning with a selected partner. Of the form "XXXXX/region/ + # domain" + # Corresponds to the JSON property `pairingKey` + # @return [String] + attr_accessor :pairing_key + + # Optional BGP ASN for the router that should be supplied by a layer 3 Partner + # if they configured BGP on behalf of the customer. Output only for PARTNER type, + # input only for PARTNER_PROVIDER, not available for DEDICATED. + # Corresponds to the JSON property `partnerAsn` + # @return [Fixnum] + attr_accessor :partner_asn + + # Informational metadata about Partner attachments from Partners to display to + # customers. These fields are propagated from PARTNER_PROVIDER attachments to + # their corresponding PARTNER attachments. + # Corresponds to the JSON property `partnerMetadata` + # @return [Google::Apis::ComputeBeta::InterconnectAttachmentPartnerMetadata] + attr_accessor :partner_metadata + # Information for an interconnect attachment when this belongs to an # interconnect of type DEDICATED. # Corresponds to the JSON property `privateInterconnectInfo` @@ -10222,6 +10278,11 @@ module Google # @return [String] attr_accessor :self_link + # [Output Only] The current state of this attachment's functionality. + # Corresponds to the JSON property `state` + # @return [String] + attr_accessor :state + # # Corresponds to the JSON property `type` # @return [String] @@ -10241,11 +10302,13 @@ module Google # Update properties of this object def update!(**args) @admin_enabled = args[:admin_enabled] if args.key?(:admin_enabled) + @bandwidth = args[:bandwidth] if args.key?(:bandwidth) @candidate_subnets = args[:candidate_subnets] if args.key?(:candidate_subnets) @cloud_router_ip_address = args[:cloud_router_ip_address] if args.key?(:cloud_router_ip_address) @creation_timestamp = args[:creation_timestamp] if args.key?(:creation_timestamp) @customer_router_ip_address = args[:customer_router_ip_address] if args.key?(:customer_router_ip_address) @description = args[:description] if args.key?(:description) + @edge_availability_domain = args[:edge_availability_domain] if args.key?(:edge_availability_domain) @google_reference_id = args[:google_reference_id] if args.key?(:google_reference_id) @id = args[:id] if args.key?(:id) @interconnect = args[:interconnect] if args.key?(:interconnect) @@ -10254,10 +10317,14 @@ module Google @labels = args[:labels] if args.key?(:labels) @name = args[:name] if args.key?(:name) @operational_status = args[:operational_status] if args.key?(:operational_status) + @pairing_key = args[:pairing_key] if args.key?(:pairing_key) + @partner_asn = args[:partner_asn] if args.key?(:partner_asn) + @partner_metadata = args[:partner_metadata] if args.key?(:partner_metadata) @private_interconnect_info = args[:private_interconnect_info] if args.key?(:private_interconnect_info) @region = args[:region] if args.key?(:region) @router = args[:router] if args.key?(:router) @self_link = args[:self_link] if args.key?(:self_link) + @state = args[:state] if args.key?(:state) @type = args[:type] if args.key?(:type) @vlan_tag8021q = args[:vlan_tag8021q] if args.key?(:vlan_tag8021q) end @@ -10500,6 +10567,44 @@ module Google end end + # Informational metadata about Partner attachments from Partners to display to + # customers. These fields are propagated from PARTNER_PROVIDER attachments to + # their corresponding PARTNER attachments. + class InterconnectAttachmentPartnerMetadata + include Google::Apis::Core::Hashable + + # Plain text name of the Interconnect this attachment is connected to, as + # displayed in the Partner?s portal. For instance ?Chicago 1?. This value may be + # validated to match approved Partner values. + # Corresponds to the JSON property `interconnectName` + # @return [String] + attr_accessor :interconnect_name + + # Plain text name of the Partner providing this attachment. This value may be + # validated to match approved Partner values. + # Corresponds to the JSON property `partnerName` + # @return [String] + attr_accessor :partner_name + + # URL of the Partner?s portal for this Attachment. Partners may customise this + # to be a deep-link to the specific resource on the Partner portal. This value + # may be validated to match approved Partner values. + # Corresponds to the JSON property `portalUrl` + # @return [String] + attr_accessor :portal_url + + def initialize(**args) + update!(**args) + end + + # Update properties of this object + def update!(**args) + @interconnect_name = args[:interconnect_name] if args.key?(:interconnect_name) + @partner_name = args[:partner_name] if args.key?(:partner_name) + @portal_url = args[:portal_url] if args.key?(:portal_url) + end + end + # Information for an interconnect attachment when this belongs to an # interconnect of type DEDICATED. class InterconnectAttachmentPrivateInfo @@ -17343,6 +17448,12 @@ module Google # @return [String] attr_accessor :description + # Whether to enable flow logging for this subnetwork. + # Corresponds to the JSON property `enableFlowLogs` + # @return [Boolean] + attr_accessor :enable_flow_logs + alias_method :enable_flow_logs?, :enable_flow_logs + # Fingerprint of this resource. A hash of the contents stored in this object. # This field is used in optimistic locking. This field will be ignored when # inserting a Subnetwork. An up-to-date fingerprint must be provided in order to @@ -17432,6 +17543,7 @@ module Google @allow_subnet_cidr_routes_overlap = args[:allow_subnet_cidr_routes_overlap] if args.key?(:allow_subnet_cidr_routes_overlap) @creation_timestamp = args[:creation_timestamp] if args.key?(:creation_timestamp) @description = args[:description] if args.key?(:description) + @enable_flow_logs = args[:enable_flow_logs] if args.key?(:enable_flow_logs) @fingerprint = args[:fingerprint] if args.key?(:fingerprint) @gateway_address = args[:gateway_address] if args.key?(:gateway_address) @id = args[:id] if args.key?(:id) diff --git a/generated/google/apis/compute_beta/representations.rb b/generated/google/apis/compute_beta/representations.rb index c323276aa..9d8c6d2b1 100644 --- a/generated/google/apis/compute_beta/representations.rb +++ b/generated/google/apis/compute_beta/representations.rb @@ -1354,6 +1354,12 @@ module Google include Google::Apis::Core::JsonObjectSupport end + class InterconnectAttachmentPartnerMetadata + class Representation < Google::Apis::Core::JsonRepresentation; end + + include Google::Apis::Core::JsonObjectSupport + end + class InterconnectAttachmentPrivateInfo class Representation < Google::Apis::Core::JsonRepresentation; end @@ -4190,6 +4196,7 @@ module Google property :description, as: 'description' collection :destination_ranges, as: 'destinationRanges' property :direction, as: 'direction' + property :disabled, as: 'disabled' property :id, :numeric_string => true, as: 'id' property :kind, as: 'kind' property :name, as: 'name' @@ -5444,6 +5451,7 @@ module Google property :provisioned_link_count, as: 'provisionedLinkCount' property :requested_link_count, as: 'requestedLinkCount' property :self_link, as: 'selfLink' + property :state, as: 'state' end end @@ -5451,11 +5459,13 @@ module Google # @private class Representation < Google::Apis::Core::JsonRepresentation property :admin_enabled, as: 'adminEnabled' + property :bandwidth, as: 'bandwidth' collection :candidate_subnets, as: 'candidateSubnets' property :cloud_router_ip_address, as: 'cloudRouterIpAddress' property :creation_timestamp, as: 'creationTimestamp' property :customer_router_ip_address, as: 'customerRouterIpAddress' property :description, as: 'description' + property :edge_availability_domain, as: 'edgeAvailabilityDomain' property :google_reference_id, as: 'googleReferenceId' property :id, :numeric_string => true, as: 'id' property :interconnect, as: 'interconnect' @@ -5464,11 +5474,16 @@ module Google hash :labels, as: 'labels' property :name, as: 'name' property :operational_status, as: 'operationalStatus' + property :pairing_key, as: 'pairingKey' + property :partner_asn, :numeric_string => true, as: 'partnerAsn' + property :partner_metadata, as: 'partnerMetadata', class: Google::Apis::ComputeBeta::InterconnectAttachmentPartnerMetadata, decorator: Google::Apis::ComputeBeta::InterconnectAttachmentPartnerMetadata::Representation + property :private_interconnect_info, as: 'privateInterconnectInfo', class: Google::Apis::ComputeBeta::InterconnectAttachmentPrivateInfo, decorator: Google::Apis::ComputeBeta::InterconnectAttachmentPrivateInfo::Representation property :region, as: 'region' property :router, as: 'router' property :self_link, as: 'selfLink' + property :state, as: 'state' property :type, as: 'type' property :vlan_tag8021q, as: 'vlanTag8021q' end @@ -5538,6 +5553,15 @@ module Google end end + class InterconnectAttachmentPartnerMetadata + # @private + class Representation < Google::Apis::Core::JsonRepresentation + property :interconnect_name, as: 'interconnectName' + property :partner_name, as: 'partnerName' + property :portal_url, as: 'portalUrl' + end + end + class InterconnectAttachmentPrivateInfo # @private class Representation < Google::Apis::Core::JsonRepresentation @@ -7300,6 +7324,7 @@ module Google property :allow_subnet_cidr_routes_overlap, as: 'allowSubnetCidrRoutesOverlap' property :creation_timestamp, as: 'creationTimestamp' property :description, as: 'description' + property :enable_flow_logs, as: 'enableFlowLogs' property :fingerprint, :base64 => true, as: 'fingerprint' property :gateway_address, as: 'gatewayAddress' property :id, :numeric_string => true, as: 'id' diff --git a/generated/google/apis/compute_beta/service.rb b/generated/google/apis/compute_beta/service.rb index 1233b374a..c237e99a9 100644 --- a/generated/google/apis/compute_beta/service.rb +++ b/generated/google/apis/compute_beta/service.rb @@ -57,25 +57,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -177,25 +174,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -254,25 +248,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -480,25 +471,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -658,25 +646,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -885,25 +870,22 @@ module Google # @param [String] zone # Name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1370,25 +1352,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1610,25 +1589,22 @@ module Google # @param [String] project # Name of the project scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1923,25 +1899,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2207,25 +2180,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2327,25 +2297,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2404,25 +2371,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2696,25 +2660,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3070,25 +3031,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3297,25 +3255,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3524,25 +3479,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3899,25 +3851,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4199,25 +4148,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4412,25 +4358,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4563,25 +4506,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4779,25 +4719,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5146,25 +5083,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5513,25 +5447,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5979,25 +5910,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6205,25 +6133,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6507,25 +6432,22 @@ module Google # @param [String] zone # The name of the zone where the managed instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7233,25 +7155,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7463,25 +7382,22 @@ module Google # @param [String] zone # The name of the zone where the instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7546,25 +7462,22 @@ module Google # included instances. # @param [Google::Apis::ComputeBeta::InstanceGroupsListInstancesRequest] instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7931,25 +7844,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8107,25 +8017,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8572,25 +8479,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8655,25 +8559,22 @@ module Google # Name of the target instance scoping this request, or '-' if the request should # span over all instances in the container. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9352,6 +9253,47 @@ module Google execute_or_queue_command(command, &block) end + # Simulates a maintenance event on the instance. + # @param [String] project + # Project ID for this request. + # @param [String] zone + # The name of the zone for this request. + # @param [String] instance + # Name of the instance scoping this request. + # @param [String] fields + # Selector specifying which fields to include in a partial response. + # @param [String] quota_user + # Available to use for quota purposes for server-side applications. Can be any + # arbitrary string assigned to a user, but should not exceed 40 characters. + # Overrides userIp if both are provided. + # @param [String] user_ip + # IP address of the site where the request originates. Use this if you want to + # enforce per-user limits. + # @param [Google::Apis::RequestOptions] options + # Request-specific options + # + # @yield [result, err] Result & error if block supplied + # @yieldparam result [Google::Apis::ComputeBeta::Operation] parsed result object + # @yieldparam err [StandardError] error object if request failed + # + # @return [Google::Apis::ComputeBeta::Operation] + # + # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried + # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification + # @raise [Google::Apis::AuthorizationError] Authorization is required + def simulate_instance_maintenance_event(project, zone, instance, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block) + command = make_simple_command(:post, '{project}/zones/{zone}/instances/{instance}/simulateMaintenanceEvent', options) + command.response_representation = Google::Apis::ComputeBeta::Operation::Representation + command.response_class = Google::Apis::ComputeBeta::Operation + command.params['project'] = project unless project.nil? + command.params['zone'] = zone unless zone.nil? + command.params['instance'] = instance unless instance.nil? + command.query['fields'] = fields unless fields.nil? + command.query['quotaUser'] = quota_user unless quota_user.nil? + command.query['userIp'] = user_ip unless user_ip.nil? + execute_or_queue_command(command, &block) + end + # Starts an instance that was stopped using the using the instances().stop # method. For more information, see Restart an instance. # @param [String] project @@ -9688,25 +9630,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9915,25 +9854,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10191,25 +10127,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10407,25 +10340,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10802,25 +10732,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10878,25 +10805,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10998,25 +10922,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11268,25 +11189,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12304,25 +12222,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12736,25 +12651,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12976,25 +12888,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13150,25 +13059,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13271,25 +13177,22 @@ module Google # @param [String] region # The name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13560,25 +13463,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14083,25 +13983,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14721,25 +14618,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14805,25 +14699,22 @@ module Google # Name of the regional instance group for which we want to list the instances. # @param [Google::Apis::ComputeBeta::RegionInstanceGroupsListInstancesRequest] region_instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15067,25 +14958,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15183,25 +15071,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15259,25 +15144,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15527,25 +15409,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15947,25 +15826,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16285,25 +16161,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16634,25 +16507,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16934,25 +16804,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17193,25 +17060,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17270,25 +17134,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17441,25 +17302,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17766,25 +17624,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17843,25 +17698,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18266,25 +18118,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18577,25 +18426,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -18911,25 +18757,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19139,25 +18982,22 @@ module Google # @param [String] zone # Name of the zone scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19372,25 +19212,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -19644,25 +19481,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20077,25 +19911,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20551,25 +20382,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20733,25 +20561,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -20961,25 +20786,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21333,25 +21155,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21600,25 +21419,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -21828,25 +21644,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -22088,25 +21901,22 @@ module Google # @param [String] zone # Name of the zone for request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -22204,25 +22014,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 diff --git a/generated/google/apis/compute_v1.rb b/generated/google/apis/compute_v1.rb index 2d9ca1c60..f727bdc53 100644 --- a/generated/google/apis/compute_v1.rb +++ b/generated/google/apis/compute_v1.rb @@ -25,7 +25,7 @@ module Google # @see https://developers.google.com/compute/docs/reference/latest/ module ComputeV1 VERSION = 'V1' - REVISION = '20180220' + REVISION = '20180314' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/compute_v1/service.rb b/generated/google/apis/compute_v1/service.rb index 5e3f3ae4f..8738cd671 100644 --- a/generated/google/apis/compute_v1/service.rb +++ b/generated/google/apis/compute_v1/service.rb @@ -57,25 +57,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -177,25 +174,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -254,25 +248,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -480,25 +471,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -557,25 +545,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -784,25 +769,22 @@ module Google # @param [String] zone # Name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1117,25 +1099,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1303,25 +1282,22 @@ module Google # @param [String] project # Name of the project scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1562,25 +1538,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1751,25 +1724,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1871,25 +1841,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -1948,25 +1915,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2240,25 +2204,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2570,25 +2531,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2756,25 +2714,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -2983,25 +2938,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3257,25 +3209,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3474,25 +3423,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3604,25 +3550,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3755,25 +3698,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -3971,25 +3911,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4297,25 +4234,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -4623,25 +4557,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5048,25 +4979,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5233,25 +5161,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5535,25 +5460,22 @@ module Google # @param [String] zone # The name of the zone where the managed instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -5973,25 +5895,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6203,25 +6122,22 @@ module Google # @param [String] zone # The name of the zone where the instance group is located. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6286,25 +6202,22 @@ module Google # included instances. # @param [Google::Apis::ComputeV1::InstanceGroupsListInstancesRequest] instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6627,25 +6540,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -6762,25 +6672,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7214,25 +7121,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -7297,25 +7201,22 @@ module Google # Name of the target instance scoping this request, or '-' if the request should # span over all instances in the container. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8286,25 +8187,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8513,25 +8411,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8630,25 +8525,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -8846,25 +8738,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9015,25 +8904,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9135,25 +9021,22 @@ module Google # @param [String] zone # The name of the zone for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -9405,25 +9288,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10348,25 +10228,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10736,25 +10613,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -10932,25 +10806,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11106,25 +10977,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11473,25 +11341,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11889,25 +11754,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -11973,25 +11835,22 @@ module Google # Name of the regional instance group for which we want to list the instances. # @param [Google::Apis::ComputeV1::RegionInstanceGroupsListInstancesRequest] region_instance_groups_list_instances_request_object # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12191,25 +12050,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12307,25 +12163,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12383,25 +12236,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -12651,25 +12501,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13027,25 +12874,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13197,25 +13041,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13456,25 +13297,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13532,25 +13370,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -13815,25 +13650,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14150,25 +13982,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14420,25 +14249,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14602,25 +14428,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -14830,25 +14653,22 @@ module Google # @param [String] zone # Name of the zone scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15019,25 +14839,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15291,25 +15108,22 @@ module Google # @param [String] region # Name of the region scoping this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -15680,25 +15494,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16056,25 +15867,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16238,25 +16046,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16466,25 +16271,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16737,25 +16539,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -16963,25 +16762,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17191,25 +16987,22 @@ module Google # @param [String] region # Name of the region for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17350,25 +17143,22 @@ module Google # @param [String] zone # Name of the zone for request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 @@ -17466,25 +17256,22 @@ module Google # @param [String] project # Project ID for this request. # @param [String] filter - # Sets a filter `expression` for filtering listed resources. Your `expression` - # must be in the format: field_name comparison_string literal_string. - # The field_name is the name of the field you want to compare. Only atomic field - # types are supported (string, number, boolean). The comparison_string must be - # either eq (equals) or ne (not equals). The literal_string is the string value - # to filter to. The literal value must be valid for the type of field you are - # filtering by (string, number, boolean). For string fields, the literal value - # is interpreted as a regular expression using RE2 syntax. The literal value - # must match the entire field. - # For example, to filter for instances that do not have a name of example- - # instance, you would use name ne example-instance. - # You can filter on nested fields. For example, you could filter on instances - # that have set the scheduling.automaticRestart field to true. Use filtering on - # nested fields to take advantage of labels to organize and search for results - # based on label values. + # A filter expression that filters resources listed in the response. The + # expression must specify the field name, a comparison operator, and the value + # that you want to use for filtering. The value must be a string, a number, or a + # boolean. The comparison 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. + # 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 eq true) (zone eq us- - # central1-f). Multiple expressions are treated as AND expressions, meaning that - # resources must match all expressions to pass the filters. + # 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). # @param [Fixnum] max_results # 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 diff --git a/generated/google/apis/container_v1beta1.rb b/generated/google/apis/container_v1beta1.rb index f94c32a41..e95988fb4 100644 --- a/generated/google/apis/container_v1beta1.rb +++ b/generated/google/apis/container_v1beta1.rb @@ -26,7 +26,7 @@ module Google # @see https://cloud.google.com/container-engine/ module ContainerV1beta1 VERSION = 'V1beta1' - REVISION = '20180223' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/container_v1beta1/classes.rb b/generated/google/apis/container_v1beta1/classes.rb index 65d1b5c6f..5f185bfa4 100644 --- a/generated/google/apis/container_v1beta1/classes.rb +++ b/generated/google/apis/container_v1beta1/classes.rb @@ -365,6 +365,13 @@ module Google # @return [Google::Apis::ContainerV1beta1::MasterAuthorizedNetworksConfig] attr_accessor :master_authorized_networks_config + # The IP prefix in CIDR notation to use for the hosted master network. + # This prefix will be used for assigning private IP addresses to the + # master or set of masters, as well as the ILB VIP. + # Corresponds to the JSON property `masterIpv4CidrBlock` + # @return [String] + attr_accessor :master_ipv4_cidr_block + # The monitoring service the cluster should use to write metrics. # Currently available options: # * `monitoring.googleapis.com` - the Google Cloud Monitoring service. @@ -421,6 +428,14 @@ module Google # @return [Google::Apis::ContainerV1beta1::PodSecurityPolicyConfig] attr_accessor :pod_security_policy_config + # If this is a private cluster setup. Private clusters are clusters that, by + # default have no external IP addresses on the nodes and where nodes and the + # master communicate over private IP addresses. + # Corresponds to the JSON property `privateCluster` + # @return [Boolean] + attr_accessor :private_cluster + alias_method :private_cluster?, :private_cluster + # The resource labels for the cluster to use to annotate any related GCE # resources. # Corresponds to the JSON property `resourceLabels` @@ -495,6 +510,7 @@ module Google @maintenance_policy = args[:maintenance_policy] if args.key?(:maintenance_policy) @master_auth = args[:master_auth] if args.key?(:master_auth) @master_authorized_networks_config = args[:master_authorized_networks_config] if args.key?(:master_authorized_networks_config) + @master_ipv4_cidr_block = args[:master_ipv4_cidr_block] if args.key?(:master_ipv4_cidr_block) @monitoring_service = args[:monitoring_service] if args.key?(:monitoring_service) @name = args[:name] if args.key?(:name) @network = args[:network] if args.key?(:network) @@ -503,6 +519,7 @@ module Google @node_ipv4_cidr_size = args[:node_ipv4_cidr_size] if args.key?(:node_ipv4_cidr_size) @node_pools = args[:node_pools] if args.key?(:node_pools) @pod_security_policy_config = args[:pod_security_policy_config] if args.key?(:pod_security_policy_config) + @private_cluster = args[:private_cluster] if args.key?(:private_cluster) @resource_labels = args[:resource_labels] if args.key?(:resource_labels) @self_link = args[:self_link] if args.key?(:self_link) @services_ipv4_cidr = args[:services_ipv4_cidr] if args.key?(:services_ipv4_cidr) diff --git a/generated/google/apis/container_v1beta1/representations.rb b/generated/google/apis/container_v1beta1/representations.rb index 43a13cd15..49232eb8d 100644 --- a/generated/google/apis/container_v1beta1/representations.rb +++ b/generated/google/apis/container_v1beta1/representations.rb @@ -426,6 +426,7 @@ module Google property :master_authorized_networks_config, as: 'masterAuthorizedNetworksConfig', class: Google::Apis::ContainerV1beta1::MasterAuthorizedNetworksConfig, decorator: Google::Apis::ContainerV1beta1::MasterAuthorizedNetworksConfig::Representation + property :master_ipv4_cidr_block, as: 'masterIpv4CidrBlock' property :monitoring_service, as: 'monitoringService' property :name, as: 'name' property :network, as: 'network' @@ -438,6 +439,7 @@ module Google property :pod_security_policy_config, as: 'podSecurityPolicyConfig', class: Google::Apis::ContainerV1beta1::PodSecurityPolicyConfig, decorator: Google::Apis::ContainerV1beta1::PodSecurityPolicyConfig::Representation + property :private_cluster, as: 'privateCluster' hash :resource_labels, as: 'resourceLabels' property :self_link, as: 'selfLink' property :services_ipv4_cidr, as: 'servicesIpv4Cidr' diff --git a/generated/google/apis/dataproc_v1.rb b/generated/google/apis/dataproc_v1.rb index 39c726335..9d09dbd3f 100644 --- a/generated/google/apis/dataproc_v1.rb +++ b/generated/google/apis/dataproc_v1.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/dataproc/ module DataprocV1 VERSION = 'V1' - REVISION = '20180306' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/dataproc_v1/service.rb b/generated/google/apis/dataproc_v1/service.rb index 571fca213..f4f0e8ed2 100644 --- a/generated/google/apis/dataproc_v1/service.rb +++ b/generated/google/apis/dataproc_v1/service.rb @@ -43,7 +43,7 @@ module Google attr_accessor :quota_user def initialize - super('https://content-dataproc.googleapis.com/', '') + super('https://dataproc.googleapis.com/', '') @batch_path = 'batch' end diff --git a/generated/google/apis/dataproc_v1beta2.rb b/generated/google/apis/dataproc_v1beta2.rb index 4ffeab17b..5843343c6 100644 --- a/generated/google/apis/dataproc_v1beta2.rb +++ b/generated/google/apis/dataproc_v1beta2.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/dataproc/ module DataprocV1beta2 VERSION = 'V1beta2' - REVISION = '20180306' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/dataproc_v1beta2/classes.rb b/generated/google/apis/dataproc_v1beta2/classes.rb index e19da5c3c..c5570099e 100644 --- a/generated/google/apis/dataproc_v1beta2/classes.rb +++ b/generated/google/apis/dataproc_v1beta2/classes.rb @@ -1322,8 +1322,10 @@ module Google class ManagedCluster include Google::Apis::Core::Hashable - # Required. The cluster name. Cluster names within a project must be unique. - # Names from deleted clusters can be reused. + # Required. The cluster name prefix. A unique cluster name will be formed by + # appending a random suffix.The name must contain only lower-case letters (a-z), + # numbers (0-9), and hyphens (-). Must begin with a letter. Cannot begin or end + # with hyphen. Must consist of between 2 and 35 characters. # Corresponds to the JSON property `clusterName` # @return [String] attr_accessor :cluster_name @@ -1337,7 +1339,7 @@ module Google # 1 and 63 characters long, and must conform to the following PCRE regular # expression: \p`Ll`\p`Lo``0,62`Label values must be between 1 and 63 characters # long, and must conform to the following PCRE regular expression: \p`Ll`\p`Lo`\ - # p`N`_-`0,63`No more than 64 labels can be associated with a given cluster. + # p`N`_-`0,63`No more than 32 labels can be associated with a given cluster. # Corresponds to the JSON property `labels` # @return [Hash] attr_accessor :labels @@ -1521,7 +1523,7 @@ module Google # and 63 characters long, and must conform to the following regular expression: \ # p`Ll`\p`Lo``0,62`Label values must be between 1 and 63 characters long, and # must conform to the following regular expression: \p`Ll`\p`Lo`\p`N`_-`0,63`No - # more than 64 labels can be associated with a given job. + # more than 32 labels can be associated with a given job. # Corresponds to the JSON property `labels` # @return [Hash] attr_accessor :labels @@ -1562,8 +1564,11 @@ module Google attr_accessor :spark_sql_job # Required. The step id. The id must be unique among all jobs within the - # template.The step id is used as prefix for job id, as job workflow-step-id - # label, and in prerequisite_step_ids field from other steps. + # template.The step id is used as prefix for job id, as job goog-dataproc- + # workflow-step-id label, and in prerequisiteStepIds field from other steps.The + # id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_), and + # hyphens (-). Cannot begin or end with underscore or hyphen. Must consist of + # between 3 and 50 characters. # Corresponds to the JSON property `stepId` # @return [String] attr_accessor :step_id @@ -2286,7 +2291,9 @@ module Google # @return [String] attr_accessor :create_time - # Required. The template id. + # Required. The template id.The id must contain only letters (a-z, A-Z), numbers + # (0-9), underscores (_), and hyphens (-). Cannot begin or end with underscore + # or hyphen. Must consist of between 3 and 50 characters. # Corresponds to the JSON property `id` # @return [String] attr_accessor :id diff --git a/generated/google/apis/dataproc_v1beta2/service.rb b/generated/google/apis/dataproc_v1beta2/service.rb index b4162d366..692142b60 100644 --- a/generated/google/apis/dataproc_v1beta2/service.rb +++ b/generated/google/apis/dataproc_v1beta2/service.rb @@ -43,7 +43,7 @@ module Google attr_accessor :quota_user def initialize - super('https://content-dataproc.googleapis.com/', '') + super('https://dataproc.googleapis.com/', '') @batch_path = 'batch' end diff --git a/generated/google/apis/deploymentmanager_alpha.rb b/generated/google/apis/deploymentmanager_alpha.rb index 63f726e1a..c37c1dba7 100644 --- a/generated/google/apis/deploymentmanager_alpha.rb +++ b/generated/google/apis/deploymentmanager_alpha.rb @@ -26,7 +26,7 @@ module Google # @see https://cloud.google.com/deployment-manager/ module DeploymentmanagerAlpha VERSION = 'Alpha' - REVISION = '20180222' + REVISION = '20180309' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/deploymentmanager_alpha/service.rb b/generated/google/apis/deploymentmanager_alpha/service.rb index cf3e091ae..6262df276 100644 --- a/generated/google/apis/deploymentmanager_alpha/service.rb +++ b/generated/google/apis/deploymentmanager_alpha/service.rb @@ -488,7 +488,7 @@ module Google # The project ID for this request. # @param [Google::Apis::DeploymentmanagerAlpha::Deployment] deployment_object # @param [String] create_policy - # + # Sets the policy to use for creating new resources. # @param [Boolean] preview # If set to true, creates a deployment and creates "shell" resources but does # not actually instantiate these resources. This allows you to preview what your diff --git a/generated/google/apis/deploymentmanager_v2.rb b/generated/google/apis/deploymentmanager_v2.rb index 1ccf1ef0d..971eb6f6f 100644 --- a/generated/google/apis/deploymentmanager_v2.rb +++ b/generated/google/apis/deploymentmanager_v2.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/deployment-manager/ module DeploymentmanagerV2 VERSION = 'V2' - REVISION = '20180222' + REVISION = '20180309' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/deploymentmanager_v2/service.rb b/generated/google/apis/deploymentmanager_v2/service.rb index b5204ffb1..876f656f3 100644 --- a/generated/google/apis/deploymentmanager_v2/service.rb +++ b/generated/google/apis/deploymentmanager_v2/service.rb @@ -217,6 +217,8 @@ module Google # @param [String] project # The project ID for this request. # @param [Google::Apis::DeploymentmanagerV2::Deployment] deployment_object + # @param [String] create_policy + # Sets the policy to use for creating new resources. # @param [Boolean] preview # If set to true, creates a deployment and creates "shell" resources but does # not actually instantiate these resources. This allows you to preview what your @@ -246,13 +248,14 @@ module Google # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification # @raise [Google::Apis::AuthorizationError] Authorization is required - def insert_deployment(project, deployment_object = nil, preview: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block) + def insert_deployment(project, deployment_object = nil, create_policy: nil, preview: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block) command = make_simple_command(:post, '{project}/global/deployments', options) command.request_representation = Google::Apis::DeploymentmanagerV2::Deployment::Representation command.request_object = deployment_object command.response_representation = Google::Apis::DeploymentmanagerV2::Operation::Representation command.response_class = Google::Apis::DeploymentmanagerV2::Operation command.params['project'] = project unless project.nil? + command.query['createPolicy'] = create_policy unless create_policy.nil? command.query['preview'] = preview unless preview.nil? command.query['fields'] = fields unless fields.nil? command.query['quotaUser'] = quota_user unless quota_user.nil? diff --git a/generated/google/apis/deploymentmanager_v2beta.rb b/generated/google/apis/deploymentmanager_v2beta.rb index 45b2916f7..904b3aced 100644 --- a/generated/google/apis/deploymentmanager_v2beta.rb +++ b/generated/google/apis/deploymentmanager_v2beta.rb @@ -26,7 +26,7 @@ module Google # @see https://developers.google.com/deployment-manager/ module DeploymentmanagerV2beta VERSION = 'V2beta' - REVISION = '20180222' + REVISION = '20180309' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/deploymentmanager_v2beta/service.rb b/generated/google/apis/deploymentmanager_v2beta/service.rb index 5978369f4..cfb908201 100644 --- a/generated/google/apis/deploymentmanager_v2beta/service.rb +++ b/generated/google/apis/deploymentmanager_v2beta/service.rb @@ -488,7 +488,7 @@ module Google # The project ID for this request. # @param [Google::Apis::DeploymentmanagerV2beta::Deployment] deployment_object # @param [String] create_policy - # + # Sets the policy to use for creating new resources. # @param [Boolean] preview # If set to true, creates a deployment and creates "shell" resources but does # not actually instantiate these resources. This allows you to preview what your diff --git a/generated/google/apis/pagespeedonline_v4.rb b/generated/google/apis/pagespeedonline_v4.rb index c1fef1996..dd225dc1e 100644 --- a/generated/google/apis/pagespeedonline_v4.rb +++ b/generated/google/apis/pagespeedonline_v4.rb @@ -23,9 +23,10 @@ module Google # Analyzes the performance of a web page and provides tailored suggestions to # make that page faster. # + # @see https://developers.google.com/speed/docs/insights/v4/getting-started module PagespeedonlineV4 VERSION = 'V4' - REVISION = '20180308' + REVISION = '20180315' end end end diff --git a/generated/google/apis/pagespeedonline_v4/service.rb b/generated/google/apis/pagespeedonline_v4/service.rb index 6b7063a56..21460bbac 100644 --- a/generated/google/apis/pagespeedonline_v4/service.rb +++ b/generated/google/apis/pagespeedonline_v4/service.rb @@ -31,6 +31,7 @@ module Google # Pagespeedonline = Google::Apis::PagespeedonlineV4 # Alias the module # service = Pagespeedonline::PagespeedonlineService.new # + # @see https://developers.google.com/speed/docs/insights/v4/getting-started class PagespeedonlineService < Google::Apis::Core::BaseService # @return [String] # API key. Your API key identifies your project and provides you with API access, diff --git a/generated/google/apis/servicemanagement_v1.rb b/generated/google/apis/servicemanagement_v1.rb index f9eb55e31..b112487a9 100644 --- a/generated/google/apis/servicemanagement_v1.rb +++ b/generated/google/apis/servicemanagement_v1.rb @@ -27,7 +27,7 @@ module Google # @see https://cloud.google.com/service-management/ module ServicemanagementV1 VERSION = 'V1' - REVISION = '20180220' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/servicemanagement_v1/service.rb b/generated/google/apis/servicemanagement_v1/service.rb index 2da33a38f..b464650a4 100644 --- a/generated/google/apis/servicemanagement_v1/service.rb +++ b/generated/google/apis/servicemanagement_v1/service.rb @@ -45,7 +45,7 @@ module Google attr_accessor :quota_user def initialize - super('https://servicemanagement.googleapis.com/', '') + super('https://content-servicemanagement.googleapis.com/', '') @batch_path = 'batch' end diff --git a/generated/google/apis/serviceuser_v1.rb b/generated/google/apis/serviceuser_v1.rb index 5f2ac53f8..a25da5d33 100644 --- a/generated/google/apis/serviceuser_v1.rb +++ b/generated/google/apis/serviceuser_v1.rb @@ -27,7 +27,7 @@ module Google # @see https://cloud.google.com/service-management/ module ServiceuserV1 VERSION = 'V1' - REVISION = '20180223' + REVISION = '20180312' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/serviceuser_v1/service.rb b/generated/google/apis/serviceuser_v1/service.rb index f05608d77..65f9bb90c 100644 --- a/generated/google/apis/serviceuser_v1/service.rb +++ b/generated/google/apis/serviceuser_v1/service.rb @@ -45,7 +45,7 @@ module Google attr_accessor :quota_user def initialize - super('https://serviceuser.googleapis.com/', '') + super('https://content-serviceuser.googleapis.com/', '') @batch_path = 'batch' end diff --git a/generated/google/apis/toolresults_v1beta3.rb b/generated/google/apis/toolresults_v1beta3.rb index 3eb523d40..61497f017 100644 --- a/generated/google/apis/toolresults_v1beta3.rb +++ b/generated/google/apis/toolresults_v1beta3.rb @@ -25,7 +25,7 @@ module Google # @see https://firebase.google.com/docs/test-lab/ module ToolresultsV1beta3 VERSION = 'V1beta3' - REVISION = '20180305' + REVISION = '20180314' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/toolresults_v1beta3/classes.rb b/generated/google/apis/toolresults_v1beta3/classes.rb index df39c135f..85530fa4f 100644 --- a/generated/google/apis/toolresults_v1beta3/classes.rb +++ b/generated/google/apis/toolresults_v1beta3/classes.rb @@ -580,8 +580,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -634,8 +636,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -1429,8 +1433,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -1849,8 +1855,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -1903,8 +1911,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -2533,8 +2543,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard @@ -2706,8 +2718,10 @@ module Google # expressed using four digits while `month`, `day`, `hour`, `min`, and `sec` are # zero-padded to two digits each. The fractional seconds, which can go up to 9 # digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix - # indicates the timezone ("UTC"); the timezone is required, though only UTC (as - # indicated by "Z") is currently supported. + # indicates the timezone ("UTC"); the timezone is required. A proto3 JSON + # serializer should always use UTC (as indicated by "Z") when printing the + # Timestamp type and a proto3 JSON parser should be able to accept both UTC and + # other timezones (as indicated by an offset). # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on # January 15, 2017. # In JavaScript, one can convert a Date object to this format using the standard diff --git a/generated/google/apis/youtube_partner_v1.rb b/generated/google/apis/youtube_partner_v1.rb index 93fa49599..8eeedba44 100644 --- a/generated/google/apis/youtube_partner_v1.rb +++ b/generated/google/apis/youtube_partner_v1.rb @@ -25,7 +25,7 @@ module Google # @see https://developers.google.com/youtube/partner/ module YoutubePartnerV1 VERSION = 'V1' - REVISION = '20180305' + REVISION = '20180312' # View and manage your assets and associated content on YouTube AUTH_YOUTUBEPARTNER = 'https://www.googleapis.com/auth/youtubepartner'