google-apis-deploymentmanager_v2beta 0.10.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 79a0babdf5a05ddc63ed91129238202b8cbaf9bb0a14524954ab1b250f6c0cfd
-  data.tar.gz: a14eeaa2ab0401818be9b62471237eb17fccf8b15b17e41d3a14a3a267eb2d2a
+  metadata.gz: 355ee2cbdf8c72ffbb2a7c07696d1665cf8c4e8b2b0e8ee3267886f7a7a560d4
+  data.tar.gz: 6278284f0c78e01421eb91ecb4769407dd6062760f8f392c1e70700304f6e6c6
 SHA512:
-  metadata.gz: 34157fd1851c272ec5e424494db01ba3696475b2742cc19ba88ab64c28af71aec4e9db7c3e673a7f2155ce53bb51cf422fa0941f55e86fec1bc6b3e89e089134
-  data.tar.gz: e1280bcf35ba9eb9e385728aff7a8c77ea90d63ffad62504a5ae5e894eb6be0c449940c9bfe27f4f08203022f1d2b69b2cffb04d47ef0d881fd67b15d50b8d3c
+  metadata.gz: 15e6078bbfafb4c8a97b7efd25d8a563a6d3f9b2bce016bb50a406d0341f476ae7edd35704af2918d30b5b5169f800ca062c4cfb6f390f7c9e58e281aa46cd32
+  data.tar.gz: f0ba514219e24201809c388f7663c52094fbf7032c1a23d970491cac82e56dc09f80e0c48845859bd5833f4355afcfe8a4ad51fe60de277ec1ee02a8931ff794

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-deploymentmanager_v2beta
 
+### v0.11.0 (2021-10-07)
+
+* Regenerated from discovery document revision 20210930
+
 ### v0.10.0 (2021-08-21)
 
 * Regenerated from discovery document revision 20210817

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

@@ -1464,7 +1464,12 @@ module Google
       
         # Associates a list of `members` to a `role`. Optionally, may specify a `
         # condition` that determines how and when the `bindings` are applied. Each of
-        # the `bindings` must contain at least one member.
+        # the `bindings` must contain at least one member. The `bindings` in a `Policy`
+        # can refer to up to 1,500 members; up to 250 of these members can be Google
+        # groups. Each occurrence of a member counts towards these limits. For example,
+        # if the `bindings` grant 50 different roles to `user:alice@example.com`, and
+        # not to any other member, then you can add another 1,450 members to the `
+        # bindings` in the `Policy`.
         # Corresponds to the JSON property `bindings`
         # @return [Array<Google::Apis::DeploymentmanagerV2beta::Binding>]
         attr_accessor :bindings

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.10.0"
+      GEM_VERSION = "0.11.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.4.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20210817"
+      REVISION = "20210930"
     end
   end
 end

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

@@ -155,20 +155,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -481,20 +485,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -805,20 +813,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -905,20 +917,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -1009,20 +1025,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -1211,20 +1231,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -1279,20 +1303,24 @@ module Google
         #   The name of the type provider for this request.
         # @param [String] filter
         #   A filter expression that filters resources listed in the response. The
-        #   expression must specify the field name, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The maximum number of results per page that should be returned. If the number
         #   of available results is larger than `maxResults`, Compute Engine returns a `
@@ -1418,20 +1446,24 @@ module Google
         #   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, a comparison operator, and the value
-        #   that you want to use for filtering. The value must be a string, a number, or a
-        #   boolean. The comparison operator must be either `=`, `!=`, `>`, or `<`. For
+        #   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`.
-        #   You can also filter nested fields. For example, you could specify `scheduling.
-        #   automaticRestart = false` to include instances only if they are not scheduled
-        #   for automatic restarts. You can use filtering 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) ```
+        #   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) ```
         # @param [Fixnum] max_results
         #   The 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.10.0
+  version: 0.11.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-08-23 00:00:00.000000000 Z
+date: 2021-10-11 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/master/generated/google-apis-deploymentmanager_v2beta/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.10.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.11.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-deploymentmanager_v2beta
 post_install_message: 
 rdoc_options: []