google-api-client 0.30.2 → 0.30.3

data/generated/google/apis/cloudresourcemanager_v1.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/resource-manager
     module CloudresourcemanagerV1
       VERSION = 'V1'
-      REVISION = '20190603'
+      REVISION = '20190610'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudresourcemanager_v1/classes.rb

@@ -1527,14 +1527,10 @@ module Google
         # the response. Filter rules are case-insensitive.
         # Organizations may be filtered by `owner.directoryCustomerId` or by
         # `domain`, where the domain is a G Suite domain, for example:
-        # clang-format off
-        # | Filter                              | Description                      |
-        # |-------------------------------------|----------------------------------|
-        # | owner.directorycustomerid:123456789 | Organizations with `owner.
-        # directory_customer_id` equal to `123456789`.|
-        # | domain:google.com                   | Organizations corresponding to the
-        # domain `google.com`.|
-        # clang-format on
+        # * Filter `owner.directorycustomerid:123456789` returns Organization
+        # resources with `owner.directory_customer_id` equal to `123456789`.
+        # * Filter `domain:google.com` returns Organization resources corresponding
+        # to the domain `google.com`.
         # This field is optional.
         # Corresponds to the JSON property `filter`
         # @return [String]

data/generated/google/apis/cloudresourcemanager_v1beta1.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/resource-manager
     module CloudresourcemanagerV1beta1
       VERSION = 'V1beta1'
-      REVISION = '20190424'
+      REVISION = '20190610'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudresourcemanager_v1beta1/service.rb

@@ -128,11 +128,10 @@ module Google
         #   the response. Filter rules are case-insensitive.
         #   Organizations may be filtered by `owner.directoryCustomerId` or by
         #   `domain`, where the domain is a G Suite domain, for example:
-        #   |Filter|Description|
-        #   |------|-----------|
-        #   |owner.directorycustomerid:123456789|Organizations with
-        #   `owner.directory_customer_id` equal to `123456789`.|
-        #   |domain:google.com|Organizations corresponding to the domain `google.com`.|
+        #   * Filter `owner.directorycustomerid:123456789` returns Organization
+        #   resources with `owner.directory_customer_id` equal to `123456789`.
+        #   * Filter `domain:google.com` returns Organization resources corresponding
+        #   to the domain `google.com`.
         #   This field is optional.
         # @param [Fixnum] page_size
         #   The maximum number of Organizations to return in the response.

data/generated/google/apis/cloudresourcemanager_v2.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/resource-manager
     module CloudresourcemanagerV2
       VERSION = 'V2'
-      REVISION = '20190603'
+      REVISION = '20190619'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudresourcemanager_v2/classes.rb

@@ -254,7 +254,7 @@ module Google
         # @return [String]
         attr_accessor :display_name
       
-        # Output only.  The lifecycle state of the folder.
+        # Output only. The lifecycle state of the folder.
         # Updates to the lifecycle_state must be performed via
         # DeleteFolder and
         # UndeleteFolder.
@@ -619,14 +619,16 @@ module Google
         # The displayName field in a query expression should use escaped quotes
         # for values that include whitespace to prevent unexpected behavior.
         # Some example queries are:
-        # |Query | Description|
-        # |----- | -----------|
-        # |displayName=Test* | Folders whose display name starts with "Test".|
-        # |lifecycleState=ACTIVE | Folders whose lifecycleState is ACTIVE.|
-        # |parent=folders/123 | Folders whose parent is "folders/123".|
-        # |parent=folders/123 AND lifecycleState=ACTIVE | Active folders whose parent
-        # is "folders/123".| |displayName=\\"Test String\\"|Folders whose display
-        # name includes both "Test" and "String".|
+        # * Query `displayName=Test*` returns Folder resources whose display name
+        # starts with "Test".
+        # * Query `lifecycleState=ACTIVE` returns Folder resources with
+        # `lifecycleState` set to `ACTIVE`.
+        # * Query `parent=folders/123` returns Folder resources that have
+        # `folders/123` as a parent resource.
+        # * Query `parent=folders/123 AND lifecycleState=ACTIVE` returns active
+        # Folder resources that have `folders/123` as a parent resource.
+        # * Query `displayName=\\"Test String\\"` returns Folder resources with
+        # display names that include both "Test" and "String".
         # Corresponds to the JSON property `query`
         # @return [String]
         attr_accessor :query

data/generated/google/apis/cloudresourcemanager_v2beta1.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/resource-manager
     module CloudresourcemanagerV2beta1
       VERSION = 'V2beta1'
-      REVISION = '20190603'
+      REVISION = '20190619'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudresourcemanager_v2beta1/classes.rb

@@ -254,7 +254,7 @@ module Google
         # @return [String]
         attr_accessor :display_name
       
-        # Output only.  The lifecycle state of the folder.
+        # Output only. The lifecycle state of the folder.
         # Updates to the lifecycle_state must be performed via
         # DeleteFolder and
         # UndeleteFolder.
@@ -619,14 +619,16 @@ module Google
         # The displayName field in a query expression should use escaped quotes
         # for values that include whitespace to prevent unexpected behavior.
         # Some example queries are:
-        # |Query | Description|
-        # |----- | -----------|
-        # |displayName=Test* | Folders whose display name starts with "Test".|
-        # |lifecycleState=ACTIVE | Folders whose lifecycleState is ACTIVE.|
-        # |parent=folders/123 | Folders whose parent is "folders/123".|
-        # |parent=folders/123 AND lifecycleState=ACTIVE | Active folders whose parent
-        # is "folders/123".| |displayName=\\"Test String\\"|Folders whose display
-        # name includes both "Test" and "String".|
+        # * Query `displayName=Test*` returns Folder resources whose display name
+        # starts with "Test".
+        # * Query `lifecycleState=ACTIVE` returns Folder resources with
+        # `lifecycleState` set to `ACTIVE`.
+        # * Query `parent=folders/123` returns Folder resources that have
+        # `folders/123` as a parent resource.
+        # * Query `parent=folders/123 AND lifecycleState=ACTIVE` returns active
+        # Folder resources that have `folders/123` as a parent resource.
+        # * Query `displayName=\\"Test String\\"` returns Folder resources with
+        # display names that include both "Test" and "String".
         # Corresponds to the JSON property `query`
         # @return [String]
         attr_accessor :query

data/generated/google/apis/cloudscheduler_v1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/scheduler/
     module CloudschedulerV1
       VERSION = 'V1'
-      REVISION = '20190429'
+      REVISION = '20190604'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudscheduler_v1/classes.rb

@@ -287,17 +287,18 @@ module Google
       
         # Contains information needed for generating an
         # [OAuth token](https://developers.google.com/identity/protocols/OAuth2).
-        # This type of authorization should be used when sending requests to a GCP
-        # endpoint.
+        # This type of authorization should generally only be used when calling Google
+        # APIs hosted on *.googleapis.com.
         # Corresponds to the JSON property `oauthToken`
         # @return [Google::Apis::CloudschedulerV1::OAuthToken]
         attr_accessor :oauth_token
       
         # Contains information needed for generating an
         # [OpenID Connect
-        # token](https://developers.google.com/identity/protocols/OpenIDConnect). This
-        # type of authorization should be used when sending requests to third party
-        # endpoints or Cloud Run.
+        # token](https://developers.google.com/identity/protocols/OpenIDConnect).
+        # This type of authorization can be used for many scenarios, including
+        # calling Cloud Run, or endpoints where you intend to validate the token
+        # yourself.
         # Corresponds to the JSON property `oidcToken`
         # @return [Google::Apis::CloudschedulerV1::OidcToken]
         attr_accessor :oidc_token
@@ -453,43 +454,10 @@ module Google
       
         # The `Status` type defines a logical error model that is suitable for
         # different programming environments, including REST APIs and RPC APIs. It is
-        # used by [gRPC](https://github.com/grpc). The error model is designed to be:
-        # - Simple to use and understand for most users
-        # - Flexible enough to meet unexpected needs
-        # # Overview
-        # The `Status` message contains three pieces of data: error code, error
-        # message, and error details. The error code should be an enum value of
-        # google.rpc.Code, but it may accept additional error codes if needed.  The
-        # error message should be a developer-facing English message that helps
-        # developers *understand* and *resolve* the error. If a localized user-facing
-        # error message is needed, put the localized message in the error details or
-        # localize it in the client. The optional error details may contain arbitrary
-        # information about the error. There is a predefined set of error detail types
-        # in the package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `Status` message is the logical representation of the error model, but it
-        # is not necessarily the actual wire format. When the `Status` message is
-        # exposed in different client libraries and different wire protocols, it can be
-        # mapped differently. For example, it will likely be mapped to some exceptions
-        # in Java, but more likely mapped to some error codes in C.
-        # # Other uses
-        # The error model and the `Status` message can be used in a variety of
-        # environments, either with or without APIs, to provide a
-        # consistent developer experience across different environments.
-        # Example uses of this error model include:
-        # - Partial errors. If a service needs to return partial errors to the client,
-        # it may embed the `Status` in the normal response to indicate the partial
-        # errors.
-        # - Workflow errors. A typical workflow has multiple steps. Each step may
-        # have a `Status` message for error reporting.
-        # - Batch operations. If a client uses batch request and batch response, the
-        # `Status` message should be used directly inside batch response, one for
-        # each error sub-response.
-        # - Asynchronous operations. If an API call embeds asynchronous operation
-        # results in its response, the status of those operations should be
-        # represented directly using the `Status` message.
-        # - Logging. If some API errors are stored in logs, the message `Status` could
-        # be used directly after any stripping needed for security/privacy reasons.
+        # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+        # three pieces of data: error code, error message, and error details.
+        # You can find out more about this error model and how to work with it in the
+        # [API Design Guide](https://cloud.google.com/apis/design/errors).
         # Corresponds to the JSON property `status`
         # @return [Google::Apis::CloudschedulerV1::Status]
         attr_accessor :status
@@ -638,8 +606,8 @@ module Google
       
       # Contains information needed for generating an
       # [OAuth token](https://developers.google.com/identity/protocols/OAuth2).
-      # This type of authorization should be used when sending requests to a GCP
-      # endpoint.
+      # This type of authorization should generally only be used when calling Google
+      # APIs hosted on *.googleapis.com.
       class OAuthToken
         include Google::Apis::Core::Hashable
       
@@ -671,9 +639,10 @@ module Google
       
       # Contains information needed for generating an
       # [OpenID Connect
-      # token](https://developers.google.com/identity/protocols/OpenIDConnect). This
-      # type of authorization should be used when sending requests to third party
-      # endpoints or Cloud Run.
+      # token](https://developers.google.com/identity/protocols/OpenIDConnect).
+      # This type of authorization can be used for many scenarios, including
+      # calling Cloud Run, or endpoints where you intend to validate the token
+      # yourself.
       class OidcToken
         include Google::Apis::Core::Hashable
       
@@ -920,43 +889,10 @@ module Google
       
       # The `Status` type defines a logical error model that is suitable for
       # different programming environments, including REST APIs and RPC APIs. It is
-      # used by [gRPC](https://github.com/grpc). The error model is designed to be:
-      # - Simple to use and understand for most users
-      # - Flexible enough to meet unexpected needs
-      # # Overview
-      # The `Status` message contains three pieces of data: error code, error
-      # message, and error details. The error code should be an enum value of
-      # google.rpc.Code, but it may accept additional error codes if needed.  The
-      # error message should be a developer-facing English message that helps
-      # developers *understand* and *resolve* the error. If a localized user-facing
-      # error message is needed, put the localized message in the error details or
-      # localize it in the client. The optional error details may contain arbitrary
-      # information about the error. There is a predefined set of error detail types
-      # in the package `google.rpc` that can be used for common error conditions.
-      # # Language mapping
-      # The `Status` message is the logical representation of the error model, but it
-      # is not necessarily the actual wire format. When the `Status` message is
-      # exposed in different client libraries and different wire protocols, it can be
-      # mapped differently. For example, it will likely be mapped to some exceptions
-      # in Java, but more likely mapped to some error codes in C.
-      # # Other uses
-      # The error model and the `Status` message can be used in a variety of
-      # environments, either with or without APIs, to provide a
-      # consistent developer experience across different environments.
-      # Example uses of this error model include:
-      # - Partial errors. If a service needs to return partial errors to the client,
-      # it may embed the `Status` in the normal response to indicate the partial
-      # errors.
-      # - Workflow errors. A typical workflow has multiple steps. Each step may
-      # have a `Status` message for error reporting.
-      # - Batch operations. If a client uses batch request and batch response, the
-      # `Status` message should be used directly inside batch response, one for
-      # each error sub-response.
-      # - Asynchronous operations. If an API call embeds asynchronous operation
-      # results in its response, the status of those operations should be
-      # represented directly using the `Status` message.
-      # - Logging. If some API errors are stored in logs, the message `Status` could
-      # be used directly after any stripping needed for security/privacy reasons.
+      # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+      # three pieces of data: error code, error message, and error details.
+      # You can find out more about this error model and how to work with it in the
+      # [API Design Guide](https://cloud.google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/cloudscheduler_v1beta1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/scheduler/
     module CloudschedulerV1beta1
       VERSION = 'V1beta1'
-      REVISION = '20190429'
+      REVISION = '20190604'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/cloudscheduler_v1beta1/classes.rb

@@ -287,17 +287,18 @@ module Google
       
         # Contains information needed for generating an
         # [OAuth token](https://developers.google.com/identity/protocols/OAuth2).
-        # This type of authorization should be used when sending requests to a GCP
-        # endpoint.
+        # This type of authorization should generally only be used when calling Google
+        # APIs hosted on *.googleapis.com.
         # Corresponds to the JSON property `oauthToken`
         # @return [Google::Apis::CloudschedulerV1beta1::OAuthToken]
         attr_accessor :oauth_token
       
         # Contains information needed for generating an
         # [OpenID Connect
-        # token](https://developers.google.com/identity/protocols/OpenIDConnect). This
-        # type of authorization should be used when sending requests to third party
-        # endpoints or Cloud Run.
+        # token](https://developers.google.com/identity/protocols/OpenIDConnect).
+        # This type of authorization can be used for many scenarios, including
+        # calling Cloud Run, or endpoints where you intend to validate the token
+        # yourself.
         # Corresponds to the JSON property `oidcToken`
         # @return [Google::Apis::CloudschedulerV1beta1::OidcToken]
         attr_accessor :oidc_token
@@ -454,43 +455,10 @@ module Google
       
         # The `Status` type defines a logical error model that is suitable for
         # different programming environments, including REST APIs and RPC APIs. It is
-        # used by [gRPC](https://github.com/grpc). The error model is designed to be:
-        # - Simple to use and understand for most users
-        # - Flexible enough to meet unexpected needs
-        # # Overview
-        # The `Status` message contains three pieces of data: error code, error
-        # message, and error details. The error code should be an enum value of
-        # google.rpc.Code, but it may accept additional error codes if needed.  The
-        # error message should be a developer-facing English message that helps
-        # developers *understand* and *resolve* the error. If a localized user-facing
-        # error message is needed, put the localized message in the error details or
-        # localize it in the client. The optional error details may contain arbitrary
-        # information about the error. There is a predefined set of error detail types
-        # in the package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `Status` message is the logical representation of the error model, but it
-        # is not necessarily the actual wire format. When the `Status` message is
-        # exposed in different client libraries and different wire protocols, it can be
-        # mapped differently. For example, it will likely be mapped to some exceptions
-        # in Java, but more likely mapped to some error codes in C.
-        # # Other uses
-        # The error model and the `Status` message can be used in a variety of
-        # environments, either with or without APIs, to provide a
-        # consistent developer experience across different environments.
-        # Example uses of this error model include:
-        # - Partial errors. If a service needs to return partial errors to the client,
-        # it may embed the `Status` in the normal response to indicate the partial
-        # errors.
-        # - Workflow errors. A typical workflow has multiple steps. Each step may
-        # have a `Status` message for error reporting.
-        # - Batch operations. If a client uses batch request and batch response, the
-        # `Status` message should be used directly inside batch response, one for
-        # each error sub-response.
-        # - Asynchronous operations. If an API call embeds asynchronous operation
-        # results in its response, the status of those operations should be
-        # represented directly using the `Status` message.
-        # - Logging. If some API errors are stored in logs, the message `Status` could
-        # be used directly after any stripping needed for security/privacy reasons.
+        # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+        # three pieces of data: error code, error message, and error details.
+        # You can find out more about this error model and how to work with it in the
+        # [API Design Guide](https://cloud.google.com/apis/design/errors).
         # Corresponds to the JSON property `status`
         # @return [Google::Apis::CloudschedulerV1beta1::Status]
         attr_accessor :status
@@ -639,8 +607,8 @@ module Google
       
       # Contains information needed for generating an
       # [OAuth token](https://developers.google.com/identity/protocols/OAuth2).
-      # This type of authorization should be used when sending requests to a GCP
-      # endpoint.
+      # This type of authorization should generally only be used when calling Google
+      # APIs hosted on *.googleapis.com.
       class OAuthToken
         include Google::Apis::Core::Hashable
       
@@ -672,9 +640,10 @@ module Google
       
       # Contains information needed for generating an
       # [OpenID Connect
-      # token](https://developers.google.com/identity/protocols/OpenIDConnect). This
-      # type of authorization should be used when sending requests to third party
-      # endpoints or Cloud Run.
+      # token](https://developers.google.com/identity/protocols/OpenIDConnect).
+      # This type of authorization can be used for many scenarios, including
+      # calling Cloud Run, or endpoints where you intend to validate the token
+      # yourself.
       class OidcToken
         include Google::Apis::Core::Hashable
       
@@ -921,43 +890,10 @@ module Google
       
       # The `Status` type defines a logical error model that is suitable for
       # different programming environments, including REST APIs and RPC APIs. It is
-      # used by [gRPC](https://github.com/grpc). The error model is designed to be:
-      # - Simple to use and understand for most users
-      # - Flexible enough to meet unexpected needs
-      # # Overview
-      # The `Status` message contains three pieces of data: error code, error
-      # message, and error details. The error code should be an enum value of
-      # google.rpc.Code, but it may accept additional error codes if needed.  The
-      # error message should be a developer-facing English message that helps
-      # developers *understand* and *resolve* the error. If a localized user-facing
-      # error message is needed, put the localized message in the error details or
-      # localize it in the client. The optional error details may contain arbitrary
-      # information about the error. There is a predefined set of error detail types
-      # in the package `google.rpc` that can be used for common error conditions.
-      # # Language mapping
-      # The `Status` message is the logical representation of the error model, but it
-      # is not necessarily the actual wire format. When the `Status` message is
-      # exposed in different client libraries and different wire protocols, it can be
-      # mapped differently. For example, it will likely be mapped to some exceptions
-      # in Java, but more likely mapped to some error codes in C.
-      # # Other uses
-      # The error model and the `Status` message can be used in a variety of
-      # environments, either with or without APIs, to provide a
-      # consistent developer experience across different environments.
-      # Example uses of this error model include:
-      # - Partial errors. If a service needs to return partial errors to the client,
-      # it may embed the `Status` in the normal response to indicate the partial
-      # errors.
-      # - Workflow errors. A typical workflow has multiple steps. Each step may
-      # have a `Status` message for error reporting.
-      # - Batch operations. If a client uses batch request and batch response, the
-      # `Status` message should be used directly inside batch response, one for
-      # each error sub-response.
-      # - Asynchronous operations. If an API call embeds asynchronous operation
-      # results in its response, the status of those operations should be
-      # represented directly using the `Status` message.
-      # - Logging. If some API errors are stored in logs, the message `Status` could
-      # be used directly after any stripping needed for security/privacy reasons.
+      # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+      # three pieces of data: error code, error message, and error details.
+      # You can find out more about this error model and how to work with it in the
+      # [API Design Guide](https://cloud.google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable