google-apis-deploymentmanager_alpha 0.10.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2a86b0cc5b0543a504a6b0ce811bc4531560423fd3454dd862ed19257ea5aada
-  data.tar.gz: 6caca3387ced87a9daeb2b90dd1eff31ab4c41bdc4d25f0f907ac99c38579842
+  metadata.gz: cc038ca6449024b3c458d72653b3e8b892efbcabc4ed3cb678b6939d58fccc39
+  data.tar.gz: 81208bc2c8f150b5f9da56df3d00586c0fcbc1ce4376704445f91c2a269df941
 SHA512:
-  metadata.gz: '0974a6a10b3f9275f5e3edb34052da69704a0fab25f41a311bd0badf06276bae8322aa619dcc15e9a56775bc88d0e652ae520f8392552cef36964db93a8b5ece'
-  data.tar.gz: 3ad7ee745e28acb24f2f8dbda5134d737c33f9c1d04f607f7f7ae9eb831c74acbb7f2998c461598c4e9003427521d1048080e89b4e37f268bb62965483027f88
+  metadata.gz: 49e958f7ad95cb13b96487bbfe928eaa0a1ea54ef4a0ad58e0b962cf5ebea3357a19199734dfed62ce06cfca331c7cf18ab3f234b1cd05f32095b8b48d3c9a4f
+  data.tar.gz: 9bfc2ccb94972db119946356756086eee0f73d08bd1514041268c654244ff8d222852fc5e8012da924d398cc537f7b6413fb87b9540749acd4a226e8645f15ec

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-deploymentmanager_alpha
 
+### 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_alpha/classes.rb

@@ -1557,7 +1557,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::DeploymentmanagerAlpha::Binding>]
         attr_accessor :bindings

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

@@ -16,13 +16,13 @@ module Google
   module Apis
     module DeploymentmanagerAlpha
       # Version of the google-apis-deploymentmanager_alpha 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_alpha/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 `
@@ -1451,20 +1479,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_alpha
 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_alpha/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_alpha/v0.10.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_alpha/v0.11.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-deploymentmanager_alpha
 post_install_message: 
 rdoc_options: []