google-apis-deploymentmanager_v2 0.15.0 → 0.16.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4efe4801ec867270c6dd14401211180c8e006ad148615e4dbb6cdb5e75082138
-  data.tar.gz: 8766c2890630f4090932c19127c050822144de1653b4bcf844f5fa6e5bcc93b1
+  metadata.gz: 4bc77fc40dac75b62fde14867bd8bd92d6852ac7b512f64b81ddf018b9043615
+  data.tar.gz: 554371aef1b0d63c15023f80f34e715a81249934b03310abd782137d61d44d8b
 SHA512:
-  metadata.gz: 87c3ff77aa6e6138e6144e65aae1b405432ad67b4bc0a54d2856043502ed659a1a328cabce6a0ee56864c689d6309de1aa960a4cc6dd3a542accde3a225fb758
-  data.tar.gz: f1115ebe4072cfa48941be90e1e11f55747fee3ac8d77b5f0511bdc974dfdca29bdf238decce872f0d99209d4c6e49be77894f8f0ee5acbae6b01ceb5c0d7ae0
+  metadata.gz: 4ac7de199d581137f7f3be1b824ccbb201e7ce93cfd16a40f61fde549ab42bbe3186b829590ee198a6d5d74310ce2087534d5d64119643771e06e8d78965a300
+  data.tar.gz: 74182c0d42c8140b1ff486ec671d7f5ce3eca7088b9ad7fa9781249b51b7a3e788c1c8f4ef488406592077960faa5b1581d20bb247e9a10f978639e340daba33

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-deploymentmanager_v2
 
+### v0.16.0 (2022-05-27)
+
+* Regenerated from discovery document revision 20220520
+
 ### v0.15.0 (2022-05-05)
 
 * Regenerated from discovery document revision 20220429

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

@@ -16,13 +16,13 @@ module Google
   module Apis
     module DeploymentmanagerV2
       # Version of the google-apis-deploymentmanager_v2 gem
-      GEM_VERSION = "0.15.0"
+      GEM_VERSION = "0.16.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.4.1"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20220429"
+      REVISION = "20220520"
     end
   end
 end

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

@@ -243,25 +243,36 @@ module Google
         # @param [String] project
         #   The project ID for this request.
         # @param [String] filter
-        #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, an operator, and the value that you
-        #   want to use for filtering. The value must be a string, a number, or a boolean.
-        #   The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
-        #   example, if you are filtering Compute Engine instances, you can exclude
-        #   instances named `example-instance` by specifying `name != example-instance`.
-        #   The `:` operator can be used with string fields to match substrings. For non-
-        #   string fields it is equivalent to the `=` operator. The `:*` comparison can be
-        #   used to test whether a key has been defined. For example, to find all objects
-        #   with `owner` label use: ``` labels.owner:* ``` You can also filter nested
-        #   fields. For example, you could specify `scheduling.automaticRestart = false`
-        #   to include instances only if they are not scheduled for automatic restarts.
-        #   You can use filtering on nested fields to filter based on resource labels. To
-        #   filter on multiple expressions, provide each separate expression within
-        #   parentheses. For example: ``` (scheduling.automaticRestart = true) (
-        #   cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
-        #   expression. However, you can include `AND` and `OR` expressions explicitly.
-        #   For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
-        #   Broadwell") AND (scheduling.automaticRestart = true) ```
+        #   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
+        #   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`.
         # @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 `
@@ -571,25 +582,36 @@ module Google
         # @param [String] deployment
         #   The name of the deployment for this request.
         # @param [String] filter
-        #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, an operator, and the value that you
-        #   want to use for filtering. The value must be a string, a number, or a boolean.
-        #   The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
-        #   example, if you are filtering Compute Engine instances, you can exclude
-        #   instances named `example-instance` by specifying `name != example-instance`.
-        #   The `:` operator can be used with string fields to match substrings. For non-
-        #   string fields it is equivalent to the `=` operator. The `:*` comparison can be
-        #   used to test whether a key has been defined. For example, to find all objects
-        #   with `owner` label use: ``` labels.owner:* ``` You can also filter nested
-        #   fields. For example, you could specify `scheduling.automaticRestart = false`
-        #   to include instances only if they are not scheduled for automatic restarts.
-        #   You can use filtering on nested fields to filter based on resource labels. To
-        #   filter on multiple expressions, provide each separate expression within
-        #   parentheses. For example: ``` (scheduling.automaticRestart = true) (
-        #   cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
-        #   expression. However, you can include `AND` and `OR` expressions explicitly.
-        #   For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
-        #   Broadwell") AND (scheduling.automaticRestart = true) ```
+        #   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
+        #   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`.
         # @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 `
@@ -675,25 +697,36 @@ module Google
         # @param [String] project
         #   The project ID for this request.
         # @param [String] filter
-        #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, an operator, and the value that you
-        #   want to use for filtering. The value must be a string, a number, or a boolean.
-        #   The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
-        #   example, if you are filtering Compute Engine instances, you can exclude
-        #   instances named `example-instance` by specifying `name != example-instance`.
-        #   The `:` operator can be used with string fields to match substrings. For non-
-        #   string fields it is equivalent to the `=` operator. The `:*` comparison can be
-        #   used to test whether a key has been defined. For example, to find all objects
-        #   with `owner` label use: ``` labels.owner:* ``` You can also filter nested
-        #   fields. For example, you could specify `scheduling.automaticRestart = false`
-        #   to include instances only if they are not scheduled for automatic restarts.
-        #   You can use filtering on nested fields to filter based on resource labels. To
-        #   filter on multiple expressions, provide each separate expression within
-        #   parentheses. For example: ``` (scheduling.automaticRestart = true) (
-        #   cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
-        #   expression. However, you can include `AND` and `OR` expressions explicitly.
-        #   For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
-        #   Broadwell") AND (scheduling.automaticRestart = true) ```
+        #   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
+        #   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`.
         # @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 `
@@ -783,25 +816,36 @@ module Google
         # @param [String] deployment
         #   The name of the deployment for this request.
         # @param [String] filter
-        #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, an operator, and the value that you
-        #   want to use for filtering. The value must be a string, a number, or a boolean.
-        #   The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
-        #   example, if you are filtering Compute Engine instances, you can exclude
-        #   instances named `example-instance` by specifying `name != example-instance`.
-        #   The `:` operator can be used with string fields to match substrings. For non-
-        #   string fields it is equivalent to the `=` operator. The `:*` comparison can be
-        #   used to test whether a key has been defined. For example, to find all objects
-        #   with `owner` label use: ``` labels.owner:* ``` You can also filter nested
-        #   fields. For example, you could specify `scheduling.automaticRestart = false`
-        #   to include instances only if they are not scheduled for automatic restarts.
-        #   You can use filtering on nested fields to filter based on resource labels. To
-        #   filter on multiple expressions, provide each separate expression within
-        #   parentheses. For example: ``` (scheduling.automaticRestart = true) (
-        #   cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
-        #   expression. However, you can include `AND` and `OR` expressions explicitly.
-        #   For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
-        #   Broadwell") AND (scheduling.automaticRestart = true) ```
+        #   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
+        #   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`.
         # @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 `
@@ -854,25 +898,36 @@ module Google
         # @param [String] project
         #   The project ID for this request.
         # @param [String] filter
-        #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, an operator, and the value that you
-        #   want to use for filtering. The value must be a string, a number, or a boolean.
-        #   The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
-        #   example, if you are filtering Compute Engine instances, you can exclude
-        #   instances named `example-instance` by specifying `name != example-instance`.
-        #   The `:` operator can be used with string fields to match substrings. For non-
-        #   string fields it is equivalent to the `=` operator. The `:*` comparison can be
-        #   used to test whether a key has been defined. For example, to find all objects
-        #   with `owner` label use: ``` labels.owner:* ``` You can also filter nested
-        #   fields. For example, you could specify `scheduling.automaticRestart = false`
-        #   to include instances only if they are not scheduled for automatic restarts.
-        #   You can use filtering on nested fields to filter based on resource labels. To
-        #   filter on multiple expressions, provide each separate expression within
-        #   parentheses. For example: ``` (scheduling.automaticRestart = true) (
-        #   cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
-        #   expression. However, you can include `AND` and `OR` expressions explicitly.
-        #   For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
-        #   Broadwell") AND (scheduling.automaticRestart = true) ```
+        #   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
+        #   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`.
         # @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_v2
 version: !ruby/object:Gem::Version
-  version: 0.15.0
+  version: 0.16.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-05-09 00:00:00.000000000 Z
+date: 2022-05-30 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_v2/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.15.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.16.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_v2
 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.3.5
+rubygems_version: 3.3.14
 signing_key: 
 specification_version: 4
 summary: Simple REST client for Cloud Deployment Manager V2 API V2