chiu
/
google-api-ruby-client
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Autogenerated update (2019-06-04) 

Update:
- androiddeviceprovisioning_v1
- docs_v1
- jobs_v3p1beta1
- youtube_analytics_v2
This commit is contained in:
Google APIs 2019-06-04 00:37:29 +00:00
parent f860b256c2
commit f5a4a19b68
7 changed files with 26 additions and 81 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
generated/google/apis/androiddeviceprovisioning_v1.rb
View File

@ -26,7 +26,7 @@ module Google
# @see https://developers.google.com/zero-touch/
module AndroiddeviceprovisioningV1
VERSION = 'V1'
REVISION = '20190503'
REVISION = '20190531'
end
end
end

82
generated/google/apis/androiddeviceprovisioning_v1/classes.rb
View File

@ -1052,43 +1052,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 `error`
# @return [Google::Apis::AndroiddeviceprovisioningV1::Status]
attr_accessor :error
@ -1289,43 +1256,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

2
generated/google/apis/docs_v1.rb
View File

@ -25,7 +25,7 @@ module Google
# @see https://developers.google.com/docs/
module DocsV1
VERSION = 'V1'
REVISION = '20190523'
REVISION = '20190530'
# View and manage your Google Docs documents
AUTH_DOCUMENTS = 'https://www.googleapis.com/auth/documents'

10
generated/google/apis/docs_v1/classes.rb
View File

@ -4623,6 +4623,8 @@ module Google
end
# A border around a table cell.
# Table cell borders cannot be transparent. To hide a table cell border, make
# its width 0.
class TableCellBorder
include Google::Apis::Core::Hashable
@ -4698,21 +4700,29 @@ module Google
attr_accessor :background_color
# A border around a table cell.
# Table cell borders cannot be transparent. To hide a table cell border, make
# its width 0.
# Corresponds to the JSON property `borderBottom`
# @return [Google::Apis::DocsV1::TableCellBorder]
attr_accessor :border_bottom
# A border around a table cell.
# Table cell borders cannot be transparent. To hide a table cell border, make
# its width 0.
# Corresponds to the JSON property `borderLeft`
# @return [Google::Apis::DocsV1::TableCellBorder]
attr_accessor :border_left
# A border around a table cell.
# Table cell borders cannot be transparent. To hide a table cell border, make
# its width 0.
# Corresponds to the JSON property `borderRight`
# @return [Google::Apis::DocsV1::TableCellBorder]
attr_accessor :border_right
# A border around a table cell.
# Table cell borders cannot be transparent. To hide a table cell border, make
# its width 0.
# Corresponds to the JSON property `borderTop`
# @return [Google::Apis::DocsV1::TableCellBorder]
attr_accessor :border_top

2
generated/google/apis/jobs_v3p1beta1.rb
View File

@ -26,7 +26,7 @@ module Google
# @see https://cloud.google.com/talent-solution/job-search/docs/
module JobsV3p1beta1
VERSION = 'V3p1beta1'
REVISION = '20190519'
REVISION = '20190531'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

7
generated/google/apis/jobs_v3p1beta1/classes.rb
View File

@ -511,14 +511,14 @@ module Google
# Optional.
# Compensation type.
# Default is CompensationUnit.OTHER_COMPENSATION_TYPE.
# Default is CompensationUnit.COMPENSATION_TYPE_UNSPECIFIED.
# Corresponds to the JSON property `type`
# @return [String]
attr_accessor :type
# Optional.
# Frequency of the specified amount.
# Default is CompensationUnit.OTHER_COMPENSATION_UNIT.
# Default is CompensationUnit.COMPENSATION_UNIT_UNSPECIFIED.
# Corresponds to the JSON property `unit`
# @return [String]
attr_accessor :unit
@ -544,7 +544,8 @@ module Google
include Google::Apis::Core::Hashable
# Optional.
# Whether to include jobs whose compensation range is unspecified.
# If set to true, jobs with unspecified compensation range fields are
# included.
# Corresponds to the JSON property `includeJobsWithUnspecifiedCompensationRange`
# @return [Boolean]
attr_accessor :include_jobs_with_unspecified_compensation_range

2
generated/google/apis/youtube_analytics_v2.rb
View File

@ -25,7 +25,7 @@ module Google
# @see https://developers.google.com/youtube/analytics
module YoutubeAnalyticsV2
VERSION = 'V2'
REVISION = '20180601'
REVISION = '20190531'
# Manage your YouTube account
AUTH_YOUTUBE = 'https://www.googleapis.com/auth/youtube'