google-apis-deploymentmanager_v2beta 0.25.0 → 0.26.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a277023da4a59320c834351c62426378dd5c189f266c0fda24591b4fc1d0b97c
-  data.tar.gz: e08d0d7d8c2c2a36b88f89d8a8c137a65fdba56a8ca259b80b3d51d0c54a136d
+  metadata.gz: ae68d32c36cb25c1ba4a734e8ddb74226552a78430171114fb5f7867c37cf4e9
+  data.tar.gz: 78ea81797f806232c191db2870bf44acbda6f8dc459e6f26209c070799434371
 SHA512:
-  metadata.gz: df649e26b6cdd2d3fd9b51b593519680c2d9e4de2ca9dd899fb627e321ca393b6fced142583aa5adeda7e5e52ca4b49e4eeef34ff131555322982415af0f3a59
-  data.tar.gz: 6da0fdb858e1e3bf7c476eeac7b862b6c1966094c15f32632fcdf98e4766071c70ac8570a1d262265e658e92897b93af13d3f9c59b0ac163b070d826ac6d6a82
+  metadata.gz: 9d7b958296e6cd1a17f14e0c213895b545911be78135a7f92c59abbf5110be3209fa07ba4e936d066231a81b2e53953464127ee956e55bc18e66f45ccb50ac7d
+  data.tar.gz: 6142b1051e830a4d410da91ca00b1fc97805b37afb99362161d3e87e8d6a6022a3c83dafa15ab3c17007b712b0c950f5960a31951a97e9e1124f1df58b92f3a0

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # 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

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.25.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 = "20230821"
+      REVISION = "20230921"
     end
   end
 end

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.25.0
+  version: 0.26.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-08-27 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.25.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: []