google-apis-deploymentmanager_v2beta 0.24.0 → 0.26.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 549303736ec5d7d93c1fd256fe5da8362004b1aac28be2c8b5810848b70943ee
-  data.tar.gz: 210ffc6e9b491cfb8d755a2cfece635e56af79ec93883acbc5ee8cb5b31ec167
+  metadata.gz: ae68d32c36cb25c1ba4a734e8ddb74226552a78430171114fb5f7867c37cf4e9
+  data.tar.gz: 78ea81797f806232c191db2870bf44acbda6f8dc459e6f26209c070799434371
 SHA512:
-  metadata.gz: 2bfa8b98c0adf2f52b32001114816e9f44565c6cef769c6a3d15055ecf3bda1f36ffd0b3a227d3e46f143872821d5e204e991fc9409e9d0eb76c55d4c5b57b52
-  data.tar.gz: 77ba44f0d84b44bb6a48779781b5587c69bf6cd9f3368b7828e045db1ee45479ed5f39159947da3fa0555cfeb2de44171528113fd687ddefc58a2c98d65b0534
+  metadata.gz: 9d7b958296e6cd1a17f14e0c213895b545911be78135a7f92c59abbf5110be3209fa07ba4e936d066231a81b2e53953464127ee956e55bc18e66f45ccb50ac7d
+  data.tar.gz: 6142b1051e830a4d410da91ca00b1fc97805b37afb99362161d3e87e8d6a6022a3c83dafa15ab3c17007b712b0c950f5960a31951a97e9e1124f1df58b92f3a0

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Release history for google-apis-deploymentmanager_v2beta
 
+### v0.26.0 (2023-10-01)
+
+* Regenerated from discovery document revision 20230921
+
+### v0.25.0 (2023-08-27)
+
+* Regenerated from discovery document revision 20230821
+
 ### v0.24.0 (2023-02-19)
 
 * Regenerated from discovery document revision 20230202

data/lib/google/apis/deploymentmanager_v2beta/classes.rb

@@ -259,6 +259,50 @@ module Google
         end
       end
       
+      # 
+      class BulkInsertOperationStatus
+        include Google::Apis::Core::Hashable
+      
+        # [Output Only] Count of VMs successfully created so far.
+        # Corresponds to the JSON property `createdVmCount`
+        # @return [Fixnum]
+        attr_accessor :created_vm_count
+      
+        # [Output Only] Count of VMs that got deleted during rollback.
+        # Corresponds to the JSON property `deletedVmCount`
+        # @return [Fixnum]
+        attr_accessor :deleted_vm_count
+      
+        # [Output Only] Count of VMs that started creating but encountered an error.
+        # Corresponds to the JSON property `failedToCreateVmCount`
+        # @return [Fixnum]
+        attr_accessor :failed_to_create_vm_count
+      
+        # [Output Only] Creation status of BulkInsert operation - information if the
+        # flow is rolling forward or rolling back.
+        # Corresponds to the JSON property `status`
+        # @return [String]
+        attr_accessor :status
+      
+        # [Output Only] Count of VMs originally planned to be created.
+        # Corresponds to the JSON property `targetVmCount`
+        # @return [Fixnum]
+        attr_accessor :target_vm_count
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @created_vm_count = args[:created_vm_count] if args.key?(:created_vm_count)
+          @deleted_vm_count = args[:deleted_vm_count] if args.key?(:deleted_vm_count)
+          @failed_to_create_vm_count = args[:failed_to_create_vm_count] if args.key?(:failed_to_create_vm_count)
+          @status = args[:status] if args.key?(:status)
+          @target_vm_count = args[:target_vm_count] if args.key?(:target_vm_count)
+        end
+      end
+      
       # CollectionOverride allows resource handling overrides for specific resources
       # within a BaseType
       class CollectionOverride
@@ -328,7 +372,7 @@ module Google
         # requests. For more information, read Handling API responses. Operations can be
         # global, regional or zonal. - For global operations, use the `globalOperations`
         # resource. - For regional operations, use the `regionOperations` resource. -
-        # For zonal operations, use the `zonalOperations` resource. For more information,
+        # For zonal operations, use the `zoneOperations` resource. For more information,
         # read Global, Regional, and Zonal Resources.
         # Corresponds to the JSON property `operation`
         # @return [Google::Apis::DeploymentmanagerV2beta::Operation]
@@ -536,7 +580,7 @@ module Google
         # requests. For more information, read Handling API responses. Operations can be
         # global, regional or zonal. - For global operations, use the `globalOperations`
         # resource. - For regional operations, use the `regionOperations` resource. -
-        # For zonal operations, use the `zonalOperations` resource. For more information,
+        # For zonal operations, use the `zoneOperations` resource. For more information,
         # read Global, Regional, and Zonal Resources.
         # Corresponds to the JSON property `operation`
         # @return [Google::Apis::DeploymentmanagerV2beta::Operation]
@@ -861,22 +905,22 @@ module Google
         # evaluates to `true`. A condition can add constraints based on attributes of
         # the request, the resource, or both. To learn which resources support
         # conditions in their IAM policies, see the [IAM documentation](https://cloud.
-        # google.com/iam/help/conditions/resource-policies). **JSON example:** ` "
+        # google.com/iam/help/conditions/resource-policies). **JSON example:** ``` ` "
         # bindings": [ ` "role": "roles/resourcemanager.organizationAdmin", "members": [
         # "user:mike@example.com", "group:admins@example.com", "domain:google.com", "
         # serviceAccount:my-project-id@appspot.gserviceaccount.com" ] `, ` "role": "
         # roles/resourcemanager.organizationViewer", "members": [ "user:eve@example.com"
         # ], "condition": ` "title": "expirable access", "description": "Does not grant
         # access after Sep 2020", "expression": "request.time < timestamp('2020-10-01T00:
-        # 00:00.000Z')", ` ` ], "etag": "BwWWja0YfJA=", "version": 3 ` **YAML example:**
-        # bindings: - members: - user:mike@example.com - group:admins@example.com -
-        # domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com
-        # role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.
-        # com role: roles/resourcemanager.organizationViewer condition: title: expirable
-        # access description: Does not grant access after Sep 2020 expression: request.
-        # time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 For
-        # a description of IAM and its features, see the [IAM documentation](https://
-        # cloud.google.com/iam/docs/).
+        # 00:00.000Z')", ` ` ], "etag": "BwWWja0YfJA=", "version": 3 ` ``` **YAML
+        # example:** ``` bindings: - members: - user:mike@example.com - group:admins@
+        # example.com - domain:google.com - serviceAccount:my-project-id@appspot.
+        # gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: -
+        # user:eve@example.com role: roles/resourcemanager.organizationViewer condition:
+        # title: expirable access description: Does not grant access after Sep 2020
+        # expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag:
+        # BwWWja0YfJA= version: 3 ``` For a description of IAM and its features, see the
+        # [IAM documentation](https://cloud.google.com/iam/docs/).
         # Corresponds to the JSON property `policy`
         # @return [Google::Apis::DeploymentmanagerV2beta::Policy]
         attr_accessor :policy
@@ -956,6 +1000,26 @@ module Google
         end
       end
       
+      # 
+      class InstancesBulkInsertOperationMetadata
+        include Google::Apis::Core::Hashable
+      
+        # Status information per location (location name is key). Example key: zones/us-
+        # central1-a
+        # Corresponds to the JSON property `perLocationStatus`
+        # @return [Hash<String,Google::Apis::DeploymentmanagerV2beta::BulkInsertOperationStatus>]
+        attr_accessor :per_location_status
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @per_location_status = args[:per_location_status] if args.key?(:per_location_status)
+        end
+      end
+      
       # 
       class Manifest
         include Google::Apis::Core::Hashable
@@ -1064,7 +1128,7 @@ module Google
       # requests. For more information, read Handling API responses. Operations can be
       # global, regional or zonal. - For global operations, use the `globalOperations`
       # resource. - For regional operations, use the `regionOperations` resource. -
-      # For zonal operations, use the `zonalOperations` resource. For more information,
+      # For zonal operations, use the `zoneOperations` resource. For more information,
       # read Global, Regional, and Zonal Resources.
       class Operation
         include Google::Apis::Core::Hashable
@@ -1123,6 +1187,11 @@ module Google
         # @return [String]
         attr_accessor :insert_time
       
+        # 
+        # Corresponds to the JSON property `instancesBulkInsertOperationMetadata`
+        # @return [Google::Apis::DeploymentmanagerV2beta::InstancesBulkInsertOperationMetadata]
+        attr_accessor :instances_bulk_insert_operation_metadata
+      
         # [Output Only] Type of the resource. Always `compute#operation` for Operation
         # resources.
         # Corresponds to the JSON property `kind`
@@ -1165,6 +1234,12 @@ module Google
         # @return [String]
         attr_accessor :self_link
       
+        # [Output Only] If the operation is for projects.setCommonInstanceMetadata, this
+        # field will contain information on all underlying zonal actions and their state.
+        # Corresponds to the JSON property `setCommonInstanceMetadataOperationMetadata`
+        # @return [Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadata]
+        attr_accessor :set_common_instance_metadata_operation_metadata
+      
         # [Output Only] The time that this operation was started by the server. This
         # value is in RFC3339 text format.
         # Corresponds to the JSON property `startTime`
@@ -1197,7 +1272,7 @@ module Google
         attr_accessor :target_link
       
         # [Output Only] User who requested the operation, for example: `user@example.com`
-        # .
+        # or `alice_smith_identifier (global/workforcePools/example-com-us-employees)`.
         # Corresponds to the JSON property `user`
         # @return [String]
         attr_accessor :user
@@ -1229,6 +1304,7 @@ module Google
           @http_error_status_code = args[:http_error_status_code] if args.key?(:http_error_status_code)
           @id = args[:id] if args.key?(:id)
           @insert_time = args[:insert_time] if args.key?(:insert_time)
+          @instances_bulk_insert_operation_metadata = args[:instances_bulk_insert_operation_metadata] if args.key?(:instances_bulk_insert_operation_metadata)
           @kind = args[:kind] if args.key?(:kind)
           @name = args[:name] if args.key?(:name)
           @operation_group_id = args[:operation_group_id] if args.key?(:operation_group_id)
@@ -1236,6 +1312,7 @@ module Google
           @progress = args[:progress] if args.key?(:progress)
           @region = args[:region] if args.key?(:region)
           @self_link = args[:self_link] if args.key?(:self_link)
+          @set_common_instance_metadata_operation_metadata = args[:set_common_instance_metadata_operation_metadata] if args.key?(:set_common_instance_metadata_operation_metadata)
           @start_time = args[:start_time] if args.key?(:start_time)
           @status = args[:status] if args.key?(:status)
           @status_message = args[:status_message] if args.key?(:status_message)
@@ -1443,22 +1520,22 @@ module Google
       # evaluates to `true`. A condition can add constraints based on attributes of
       # the request, the resource, or both. To learn which resources support
       # conditions in their IAM policies, see the [IAM documentation](https://cloud.
-      # google.com/iam/help/conditions/resource-policies). **JSON example:** ` "
+      # google.com/iam/help/conditions/resource-policies). **JSON example:** ``` ` "
       # bindings": [ ` "role": "roles/resourcemanager.organizationAdmin", "members": [
       # "user:mike@example.com", "group:admins@example.com", "domain:google.com", "
       # serviceAccount:my-project-id@appspot.gserviceaccount.com" ] `, ` "role": "
       # roles/resourcemanager.organizationViewer", "members": [ "user:eve@example.com"
       # ], "condition": ` "title": "expirable access", "description": "Does not grant
       # access after Sep 2020", "expression": "request.time < timestamp('2020-10-01T00:
-      # 00:00.000Z')", ` ` ], "etag": "BwWWja0YfJA=", "version": 3 ` **YAML example:**
-      # bindings: - members: - user:mike@example.com - group:admins@example.com -
-      # domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com
-      # role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.
-      # com role: roles/resourcemanager.organizationViewer condition: title: expirable
-      # access description: Does not grant access after Sep 2020 expression: request.
-      # time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 For
-      # a description of IAM and its features, see the [IAM documentation](https://
-      # cloud.google.com/iam/docs/).
+      # 00:00.000Z')", ` ` ], "etag": "BwWWja0YfJA=", "version": 3 ` ``` **YAML
+      # example:** ``` bindings: - members: - user:mike@example.com - group:admins@
+      # example.com - domain:google.com - serviceAccount:my-project-id@appspot.
+      # gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: -
+      # user:eve@example.com role: roles/resourcemanager.organizationViewer condition:
+      # title: expirable access description: Does not grant access after Sep 2020
+      # expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag:
+      # BwWWja0YfJA= version: 3 ``` For a description of IAM and its features, see the
+      # [IAM documentation](https://cloud.google.com/iam/docs/).
       class Policy
         include Google::Apis::Core::Hashable
       
@@ -1974,6 +2051,102 @@ module Google
         end
       end
       
+      # 
+      class SetCommonInstanceMetadataOperationMetadata
+        include Google::Apis::Core::Hashable
+      
+        # [Output Only] The client operation id.
+        # Corresponds to the JSON property `clientOperationId`
+        # @return [String]
+        attr_accessor :client_operation_id
+      
+        # [Output Only] Status information per location (location name is key). Example
+        # key: zones/us-central1-a
+        # Corresponds to the JSON property `perLocationOperations`
+        # @return [Hash<String,Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo>]
+        attr_accessor :per_location_operations
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @client_operation_id = args[:client_operation_id] if args.key?(:client_operation_id)
+          @per_location_operations = args[:per_location_operations] if args.key?(:per_location_operations)
+        end
+      end
+      
+      # 
+      class SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo
+        include Google::Apis::Core::Hashable
+      
+        # The `Status` type defines a logical error model that is suitable for different
+        # programming environments, including REST APIs and RPC APIs. It is used by [
+        # gRPC](https://github.com/grpc). Each `Status` message contains three pieces of
+        # data: error code, error message, and error details. You can find out more
+        # about this error model and how to work with it in the [API Design Guide](https:
+        # //cloud.google.com/apis/design/errors).
+        # Corresponds to the JSON property `error`
+        # @return [Google::Apis::DeploymentmanagerV2beta::Status]
+        attr_accessor :error
+      
+        # [Output Only] Status of the action, which can be one of the following: `
+        # PROPAGATING`, `PROPAGATED`, `ABANDONED`, `FAILED`, or `DONE`.
+        # Corresponds to the JSON property `state`
+        # @return [String]
+        attr_accessor :state
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @error = args[:error] if args.key?(:error)
+          @state = args[:state] if args.key?(:state)
+        end
+      end
+      
+      # The `Status` type defines a logical error model that is suitable for different
+      # programming environments, including REST APIs and RPC APIs. It is used by [
+      # gRPC](https://github.com/grpc). Each `Status` message contains three pieces of
+      # data: error code, error message, and error details. You can find out more
+      # about this error model and how to work with it in the [API Design Guide](https:
+      # //cloud.google.com/apis/design/errors).
+      class Status
+        include Google::Apis::Core::Hashable
+      
+        # The status code, which should be an enum value of google.rpc.Code.
+        # Corresponds to the JSON property `code`
+        # @return [Fixnum]
+        attr_accessor :code
+      
+        # A list of messages that carry the error details. There is a common set of
+        # message types for APIs to use.
+        # Corresponds to the JSON property `details`
+        # @return [Array<Hash<String,Object>>]
+        attr_accessor :details
+      
+        # A developer-facing error message, which should be in English. Any user-facing
+        # error message should be localized and sent in the google.rpc.Status.details
+        # field, or localized by the client.
+        # Corresponds to the JSON property `message`
+        # @return [String]
+        attr_accessor :message
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @code = args[:code] if args.key?(:code)
+          @details = args[:details] if args.key?(:details)
+          @message = args[:message] if args.key?(:message)
+        end
+      end
+      
       # 
       class TargetConfiguration
         include Google::Apis::Core::Hashable
@@ -2130,7 +2303,7 @@ module Google
         # requests. For more information, read Handling API responses. Operations can be
         # global, regional or zonal. - For global operations, use the `globalOperations`
         # resource. - For regional operations, use the `regionOperations` resource. -
-        # For zonal operations, use the `zonalOperations` resource. For more information,
+        # For zonal operations, use the `zoneOperations` resource. For more information,
         # read Global, Regional, and Zonal Resources.
         # Corresponds to the JSON property `operation`
         # @return [Google::Apis::DeploymentmanagerV2beta::Operation]
@@ -2343,7 +2516,7 @@ module Google
         # requests. For more information, read Handling API responses. Operations can be
         # global, regional or zonal. - For global operations, use the `globalOperations`
         # resource. - For regional operations, use the `regionOperations` resource. -
-        # For zonal operations, use the `zonalOperations` resource. For more information,
+        # For zonal operations, use the `zoneOperations` resource. For more information,
         # read Global, Regional, and Zonal Resources.
         # Corresponds to the JSON property `operation`
         # @return [Google::Apis::DeploymentmanagerV2beta::Operation]

data/lib/google/apis/deploymentmanager_v2beta/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module DeploymentmanagerV2beta
       # Version of the google-apis-deploymentmanager_v2beta gem
-      GEM_VERSION = "0.24.0"
+      GEM_VERSION = "0.26.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.12.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20230202"
+      REVISION = "20230921"
     end
   end
 end

data/lib/google/apis/deploymentmanager_v2beta/representations.rb

@@ -58,6 +58,12 @@ module Google
         include Google::Apis::Core::JsonObjectSupport
       end
       
+      class BulkInsertOperationStatus
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
       class CollectionOverride
         class Representation < Google::Apis::Core::JsonRepresentation; end
       
@@ -166,6 +172,12 @@ module Google
         include Google::Apis::Core::JsonObjectSupport
       end
       
+      class InstancesBulkInsertOperationMetadata
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
       class Manifest
         class Representation < Google::Apis::Core::JsonRepresentation; end
       
@@ -298,6 +310,24 @@ module Google
         include Google::Apis::Core::JsonObjectSupport
       end
       
+      class SetCommonInstanceMetadataOperationMetadata
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
+      class SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
+      class Status
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
       class TargetConfiguration
         class Representation < Google::Apis::Core::JsonRepresentation; end
       
@@ -439,6 +469,17 @@ module Google
         end
       end
       
+      class BulkInsertOperationStatus
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :created_vm_count, as: 'createdVmCount'
+          property :deleted_vm_count, as: 'deletedVmCount'
+          property :failed_to_create_vm_count, as: 'failedToCreateVmCount'
+          property :status, as: 'status'
+          property :target_vm_count, as: 'targetVmCount'
+        end
+      end
+      
       class CollectionOverride
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
@@ -619,6 +660,14 @@ module Google
         end
       end
       
+      class InstancesBulkInsertOperationMetadata
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          hash :per_location_status, as: 'perLocationStatus', class: Google::Apis::DeploymentmanagerV2beta::BulkInsertOperationStatus, decorator: Google::Apis::DeploymentmanagerV2beta::BulkInsertOperationStatus::Representation
+      
+        end
+      end
+      
       class Manifest
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
@@ -659,6 +708,8 @@ module Google
           property :http_error_status_code, as: 'httpErrorStatusCode'
           property :id, :numeric_string => true, as: 'id'
           property :insert_time, as: 'insertTime'
+          property :instances_bulk_insert_operation_metadata, as: 'instancesBulkInsertOperationMetadata', class: Google::Apis::DeploymentmanagerV2beta::InstancesBulkInsertOperationMetadata, decorator: Google::Apis::DeploymentmanagerV2beta::InstancesBulkInsertOperationMetadata::Representation
+      
           property :kind, as: 'kind'
           property :name, as: 'name'
           property :operation_group_id, as: 'operationGroupId'
@@ -666,6 +717,8 @@ module Google
           property :progress, as: 'progress'
           property :region, as: 'region'
           property :self_link, as: 'selfLink'
+          property :set_common_instance_metadata_operation_metadata, as: 'setCommonInstanceMetadataOperationMetadata', class: Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadata, decorator: Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadata::Representation
+      
           property :start_time, as: 'startTime'
           property :status, as: 'status'
           property :status_message, as: 'statusMessage'
@@ -873,6 +926,33 @@ module Google
         end
       end
       
+      class SetCommonInstanceMetadataOperationMetadata
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :client_operation_id, as: 'clientOperationId'
+          hash :per_location_operations, as: 'perLocationOperations', class: Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo, decorator: Google::Apis::DeploymentmanagerV2beta::SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo::Representation
+      
+        end
+      end
+      
+      class SetCommonInstanceMetadataOperationMetadataPerLocationOperationInfo
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :error, as: 'error', class: Google::Apis::DeploymentmanagerV2beta::Status, decorator: Google::Apis::DeploymentmanagerV2beta::Status::Representation
+      
+          property :state, as: 'state'
+        end
+      end
+      
+      class Status
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :code, as: 'code'
+          collection :details, as: 'details'
+          property :message, as: 'message'
+        end
+      end
+      
       class TargetConfiguration
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation

data/lib/google/apis/deploymentmanager_v2beta/service.rb

@@ -157,33 +157,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -498,33 +499,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -837,33 +839,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -952,33 +955,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -1071,33 +1075,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -1288,33 +1293,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -1371,33 +1377,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `
@@ -1525,33 +1532,34 @@ module Google
         #   A filter expression that filters resources listed in the response. Most
         #   Compute resources support two types of filter expressions: expressions that
         #   support regular expressions and expressions that follow API improvement
-        #   proposal AIP-160. If you want to use AIP-160, your expression must specify the
-        #   field name, an operator, and the value that you want to use for filtering. The
-        #   value must be a string, a number, or a boolean. The operator must be either `=`
-        #   , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
+        #   proposal AIP-160. These two types of filter expressions cannot be mixed in one
+        #   request. If you want to use AIP-160, your expression must specify the field
+        #   name, an operator, and the value that you want to use for filtering. The value
+        #   must be a string, a number, or a boolean. The operator must be either `=`, `!=`
+        #   , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
         #   Engine instances, you can exclude instances named `example-instance` by
-        #   specifying `name != example-instance`. The `:` operator can be used with
-        #   string fields to match substrings. For non-string fields it is equivalent to
-        #   the `=` operator. The `:*` comparison can be used to test whether a key has
-        #   been defined. For example, to find all objects with `owner` label use: ```
-        #   labels.owner:* ``` You can also filter nested fields. For example, you could
-        #   specify `scheduling.automaticRestart = false` to include instances only if
-        #   they are not scheduled for automatic restarts. You can use filtering on nested
-        #   fields to filter based on resource labels. To filter on multiple expressions,
-        #   provide each separate expression within parentheses. For example: ``` (
-        #   scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
-        #   default, each expression is an `AND` expression. However, you can include `AND`
-        #   and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
-        #   Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
-        #   automaticRestart = true) ``` If you want to use a regular expression, use the `
-        #   eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
-        #   expression with or without quotes or against multiple parenthesized
-        #   expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
-        #   quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
-        #   literal) (fieldname2 ne "literal")` The literal value is interpreted as a
-        #   regular expression using Google RE2 library syntax. The literal value must
-        #   match the entire field. For example, to filter for instances that do not end
-        #   with name "instance", you would use `name ne .*instance`.
+        #   specifying `name != example-instance`. The `:*` comparison can be used to test
+        #   whether a key has been defined. For example, to find all objects with `owner`
+        #   label use: ``` labels.owner:* ``` You can also filter nested fields. For
+        #   example, you could specify `scheduling.automaticRestart = false` to include
+        #   instances only if they are not scheduled for automatic restarts. You can use
+        #   filtering on nested fields to filter based on resource labels. To filter on
+        #   multiple expressions, provide each separate expression within parentheses. For
+        #   example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
+        #   Skylake") ``` By default, each expression is an `AND` expression. However, you
+        #   can include `AND` and `OR` expressions explicitly. For example: ``` (
+        #   cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
+        #   scheduling.automaticRestart = true) ``` If you want to use a regular
+        #   expression, use the `eq` (equal) or `ne` (not equal) operator against a single
+        #   un-parenthesized expression with or without quotes or against multiple
+        #   parenthesized expressions. Examples: `fieldname eq unquoted literal` `
+        #   fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
+        #   fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
+        #   interpreted as a regular expression using Google RE2 library syntax. The
+        #   literal value must match the entire field. For example, to filter for
+        #   instances that do not end with name "instance", you would use `name ne .*
+        #   instance`. You cannot combine constraints on multiple fields using regular
+        #   expressions.
         # @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 `

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-deploymentmanager_v2beta
 version: !ruby/object:Gem::Version
-  version: 0.24.0
+  version: 0.26.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-02-19 00:00:00.000000000 Z
+date: 2023-10-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_v2beta/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.24.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.26.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_v2beta
 post_install_message: 
 rdoc_options: []
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.2
+rubygems_version: 3.4.19
 signing_key: 
 specification_version: 4
 summary: Simple REST client for Cloud Deployment Manager V2 API V2beta