google-api-client 0.30.2 → 0.30.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +90 -0
- data/README.md +17 -1
- data/generated/google/apis/accesscontextmanager_v1beta.rb +1 -1
- data/generated/google/apis/accesscontextmanager_v1beta/classes.rb +108 -0
- data/generated/google/apis/accesscontextmanager_v1beta/representations.rb +48 -0
- data/generated/google/apis/adexchangebuyer_v1_3.rb +1 -1
- data/generated/google/apis/adexchangebuyer_v1_3/classes.rb +32 -6
- data/generated/google/apis/adexchangebuyer_v1_3/representations.rb +16 -1
- data/generated/google/apis/adexchangebuyer_v1_4.rb +1 -1
- data/generated/google/apis/adexchangebuyer_v1_4/classes.rb +32 -6
- data/generated/google/apis/adexchangebuyer_v1_4/representations.rb +16 -1
- data/generated/google/apis/analytics_v3.rb +1 -1
- data/generated/google/apis/analytics_v3/classes.rb +1 -1
- data/generated/google/apis/analytics_v3/service.rb +1 -1
- data/generated/google/apis/androidmanagement_v1.rb +1 -1
- data/generated/google/apis/androidmanagement_v1/classes.rb +8 -64
- data/generated/google/apis/androidpublisher_v1_1.rb +1 -1
- data/generated/google/apis/androidpublisher_v1_1/classes.rb +1 -0
- data/generated/google/apis/androidpublisher_v2.rb +1 -1
- data/generated/google/apis/androidpublisher_v2/classes.rb +6 -4
- data/generated/google/apis/androidpublisher_v3.rb +1 -1
- data/generated/google/apis/androidpublisher_v3/classes.rb +6 -4
- data/generated/google/apis/bigquery_v2.rb +1 -1
- data/generated/google/apis/bigquery_v2/classes.rb +243 -5
- data/generated/google/apis/bigquery_v2/representations.rb +77 -0
- data/generated/google/apis/bigquery_v2/service.rb +206 -0
- data/generated/google/apis/bigquerydatatransfer_v1.rb +1 -1
- data/generated/google/apis/bigquerydatatransfer_v1/classes.rb +18 -76
- data/generated/google/apis/bigquerydatatransfer_v1/representations.rb +1 -0
- data/generated/google/apis/bigquerydatatransfer_v1/service.rb +4 -4
- data/generated/google/apis/bigtableadmin_v1.rb +1 -1
- data/generated/google/apis/bigtableadmin_v1/classes.rb +0 -72
- data/generated/google/apis/bigtableadmin_v1/representations.rb +0 -32
- data/generated/google/apis/bigtableadmin_v1/service.rb +0 -69
- data/generated/google/apis/bigtableadmin_v2.rb +1 -1
- data/generated/google/apis/bigtableadmin_v2/classes.rb +72 -0
- data/generated/google/apis/bigtableadmin_v2/representations.rb +32 -0
- data/generated/google/apis/bigtableadmin_v2/service.rb +69 -0
- data/generated/google/apis/cloudasset_v1.rb +1 -1
- data/generated/google/apis/cloudasset_v1/classes.rb +9 -75
- data/generated/google/apis/cloudasset_v1beta1.rb +1 -1
- data/generated/google/apis/cloudasset_v1beta1/classes.rb +9 -75
- data/generated/google/apis/cloudfunctions_v1.rb +1 -1
- data/generated/google/apis/cloudfunctions_v1/classes.rb +8 -74
- data/generated/google/apis/cloudfunctions_v1beta2.rb +1 -1
- data/generated/google/apis/cloudfunctions_v1beta2/classes.rb +8 -74
- data/generated/google/apis/cloudiot_v1.rb +1 -1
- data/generated/google/apis/cloudiot_v1/classes.rb +8 -74
- data/generated/google/apis/cloudresourcemanager_v1.rb +1 -1
- data/generated/google/apis/cloudresourcemanager_v1/classes.rb +4 -8
- data/generated/google/apis/cloudresourcemanager_v1beta1.rb +1 -1
- data/generated/google/apis/cloudresourcemanager_v1beta1/service.rb +4 -5
- data/generated/google/apis/cloudresourcemanager_v2.rb +1 -1
- data/generated/google/apis/cloudresourcemanager_v2/classes.rb +11 -9
- data/generated/google/apis/cloudresourcemanager_v2beta1.rb +1 -1
- data/generated/google/apis/cloudresourcemanager_v2beta1/classes.rb +11 -9
- data/generated/google/apis/cloudscheduler_v1.rb +1 -1
- data/generated/google/apis/cloudscheduler_v1/classes.rb +20 -84
- data/generated/google/apis/cloudscheduler_v1beta1.rb +1 -1
- data/generated/google/apis/cloudscheduler_v1beta1/classes.rb +20 -84
- data/generated/google/apis/cloudsearch_v1.rb +1 -1
- data/generated/google/apis/cloudsearch_v1/classes.rb +8 -74
- data/generated/google/apis/cloudshell_v1.rb +1 -1
- data/generated/google/apis/cloudshell_v1/classes.rb +8 -74
- data/generated/google/apis/cloudshell_v1alpha1.rb +1 -1
- data/generated/google/apis/cloudshell_v1alpha1/classes.rb +8 -74
- data/generated/google/apis/cloudtasks_v2beta2.rb +1 -1
- data/generated/google/apis/cloudtasks_v2beta2/classes.rb +8 -0
- data/generated/google/apis/cloudtrace_v2.rb +1 -1
- data/generated/google/apis/cloudtrace_v2/classes.rb +8 -74
- data/generated/google/apis/commentanalyzer_v1alpha1.rb +2 -2
- data/generated/google/apis/commentanalyzer_v1alpha1/service.rb +1 -1
- data/generated/google/apis/composer_v1.rb +1 -1
- data/generated/google/apis/composer_v1/classes.rb +8 -74
- data/generated/google/apis/composer_v1beta1.rb +1 -1
- data/generated/google/apis/composer_v1beta1/classes.rb +8 -74
- data/generated/google/apis/compute_alpha.rb +1 -1
- data/generated/google/apis/compute_alpha/classes.rb +1991 -700
- data/generated/google/apis/compute_alpha/representations.rb +604 -154
- data/generated/google/apis/compute_alpha/service.rb +693 -89
- data/generated/google/apis/compute_beta.rb +1 -1
- data/generated/google/apis/compute_beta/classes.rb +375 -230
- data/generated/google/apis/compute_beta/representations.rb +2 -0
- data/generated/google/apis/compute_beta/service.rb +92 -6
- data/generated/google/apis/compute_v1.rb +1 -1
- data/generated/google/apis/compute_v1/classes.rb +1827 -239
- data/generated/google/apis/compute_v1/representations.rb +669 -2
- data/generated/google/apis/compute_v1/service.rb +1150 -6
- data/generated/google/apis/container_v1.rb +1 -1
- data/generated/google/apis/container_v1/classes.rb +104 -0
- data/generated/google/apis/container_v1/representations.rb +48 -0
- data/generated/google/apis/container_v1beta1.rb +1 -1
- data/generated/google/apis/container_v1beta1/classes.rb +67 -2
- data/generated/google/apis/container_v1beta1/representations.rb +31 -0
- data/generated/google/apis/content_v2.rb +1 -1
- data/generated/google/apis/content_v2/classes.rb +4 -0
- data/generated/google/apis/content_v2_1.rb +1 -1
- data/generated/google/apis/content_v2_1/classes.rb +41 -0
- data/generated/google/apis/content_v2_1/representations.rb +19 -0
- data/generated/google/apis/dataflow_v1b3.rb +1 -1
- data/generated/google/apis/dataflow_v1b3/classes.rb +46 -74
- data/generated/google/apis/dataflow_v1b3/representations.rb +17 -0
- data/generated/google/apis/datafusion_v1beta1.rb +1 -1
- data/generated/google/apis/datafusion_v1beta1/classes.rb +8 -74
- data/generated/google/apis/dataproc_v1.rb +1 -1
- data/generated/google/apis/dataproc_v1/classes.rb +147 -64
- data/generated/google/apis/dataproc_v1/representations.rb +42 -0
- data/generated/google/apis/dataproc_v1beta2.rb +1 -1
- data/generated/google/apis/dataproc_v1beta2/classes.rb +8 -64
- data/generated/google/apis/dataproc_v1beta2/service.rb +4 -2
- data/generated/google/apis/dialogflow_v2.rb +2 -2
- data/generated/google/apis/dialogflow_v2/classes.rb +32 -32
- data/generated/google/apis/dialogflow_v2/representations.rb +2 -0
- data/generated/google/apis/dialogflow_v2/service.rb +77 -17
- data/generated/google/apis/dialogflow_v2beta1.rb +2 -2
- data/generated/google/apis/dialogflow_v2beta1/classes.rb +32 -32
- data/generated/google/apis/dialogflow_v2beta1/representations.rb +2 -0
- data/generated/google/apis/dialogflow_v2beta1/service.rb +79 -19
- data/generated/google/apis/dlp_v2.rb +1 -1
- data/generated/google/apis/dlp_v2/classes.rb +4 -3
- data/generated/google/apis/dns_v1beta2.rb +1 -1
- data/generated/google/apis/dns_v1beta2/service.rb +1 -1
- data/generated/google/apis/docs_v1.rb +1 -1
- data/generated/google/apis/docs_v1/classes.rb +0 -10
- data/generated/google/apis/doubleclickbidmanager_v1.rb +1 -1
- data/generated/google/apis/file_v1.rb +1 -1
- data/generated/google/apis/file_v1/classes.rb +17 -74
- data/generated/google/apis/file_v1/representations.rb +1 -0
- data/generated/google/apis/file_v1beta1.rb +1 -1
- data/generated/google/apis/file_v1beta1/classes.rb +17 -74
- data/generated/google/apis/file_v1beta1/representations.rb +1 -0
- data/generated/google/apis/firebase_v1beta1.rb +44 -0
- data/generated/google/apis/firebase_v1beta1/classes.rb +1063 -0
- data/generated/google/apis/firebase_v1beta1/representations.rb +432 -0
- data/generated/google/apis/firebase_v1beta1/service.rb +1105 -0
- data/generated/google/apis/healthcare_v1alpha2.rb +1 -1
- data/generated/google/apis/healthcare_v1alpha2/service.rb +43 -61
- data/generated/google/apis/healthcare_v1beta1.rb +1 -1
- data/generated/google/apis/healthcare_v1beta1/service.rb +43 -61
- data/generated/google/apis/iam_v1.rb +1 -1
- data/generated/google/apis/iam_v1/classes.rb +6 -0
- data/generated/google/apis/iam_v1/representations.rb +1 -0
- data/generated/google/apis/logging_v2.rb +1 -1
- data/generated/google/apis/ml_v1.rb +1 -1
- data/generated/google/apis/ml_v1/classes.rb +18 -0
- data/generated/google/apis/ml_v1/representations.rb +3 -0
- data/generated/google/apis/monitoring_v3.rb +1 -1
- data/generated/google/apis/monitoring_v3/classes.rb +1 -1
- data/generated/google/apis/people_v1.rb +1 -1
- data/generated/google/apis/people_v1/classes.rb +12 -111
- data/generated/google/apis/pubsub_v1.rb +1 -1
- data/generated/google/apis/pubsub_v1/classes.rb +43 -0
- data/generated/google/apis/pubsub_v1/representations.rb +16 -0
- data/generated/google/apis/remotebuildexecution_v1.rb +1 -1
- data/generated/google/apis/remotebuildexecution_v1/classes.rb +89 -26
- data/generated/google/apis/remotebuildexecution_v1/representations.rb +3 -0
- data/generated/google/apis/remotebuildexecution_v1alpha.rb +1 -1
- data/generated/google/apis/remotebuildexecution_v1alpha/classes.rb +89 -26
- data/generated/google/apis/remotebuildexecution_v1alpha/representations.rb +3 -0
- data/generated/google/apis/remotebuildexecution_v1alpha/service.rb +15 -1
- data/generated/google/apis/remotebuildexecution_v2.rb +1 -1
- data/generated/google/apis/remotebuildexecution_v2/classes.rb +103 -30
- data/generated/google/apis/remotebuildexecution_v2/representations.rb +3 -0
- data/generated/google/apis/remotebuildexecution_v2/service.rb +29 -2
- data/generated/google/apis/serviceconsumermanagement_v1.rb +1 -1
- data/generated/google/apis/serviceconsumermanagement_v1/classes.rb +0 -1
- data/generated/google/apis/servicecontrol_v1.rb +1 -1
- data/generated/google/apis/servicecontrol_v1/classes.rb +64 -148
- data/generated/google/apis/servicecontrol_v1/representations.rb +17 -0
- data/generated/google/apis/servicemanagement_v1.rb +1 -1
- data/generated/google/apis/servicemanagement_v1/classes.rb +8 -74
- data/generated/google/apis/servicemanagement_v1/service.rb +9 -1
- data/generated/google/apis/servicenetworking_v1.rb +1 -1
- data/generated/google/apis/servicenetworking_v1/classes.rb +0 -1
- data/generated/google/apis/servicenetworking_v1beta.rb +1 -1
- data/generated/google/apis/servicenetworking_v1beta/classes.rb +0 -1
- data/generated/google/apis/serviceusage_v1.rb +1 -1
- data/generated/google/apis/serviceusage_v1/classes.rb +0 -1
- data/generated/google/apis/serviceusage_v1beta1.rb +1 -1
- data/generated/google/apis/serviceusage_v1beta1/classes.rb +0 -1
- data/generated/google/apis/spanner_v1.rb +1 -1
- data/generated/google/apis/spanner_v1/classes.rb +12 -111
- data/generated/google/apis/speech_v1.rb +1 -1
- data/generated/google/apis/speech_v1/classes.rb +13 -74
- data/generated/google/apis/speech_v1p1beta1.rb +1 -1
- data/generated/google/apis/speech_v1p1beta1/classes.rb +13 -74
- data/generated/google/apis/sqladmin_v1beta4.rb +1 -1
- data/generated/google/apis/sqladmin_v1beta4/classes.rb +10 -3
- data/generated/google/apis/sqladmin_v1beta4/representations.rb +1 -0
- data/generated/google/apis/tagmanager_v1.rb +4 -3
- data/generated/google/apis/tagmanager_v1/classes.rb +237 -70
- data/generated/google/apis/tagmanager_v1/service.rb +223 -374
- data/generated/google/apis/tagmanager_v2.rb +4 -3
- data/generated/google/apis/tagmanager_v2/classes.rb +221 -208
- data/generated/google/apis/tagmanager_v2/representations.rb +1 -16
- data/generated/google/apis/tagmanager_v2/service.rb +608 -757
- data/generated/google/apis/texttospeech_v1.rb +1 -1
- data/generated/google/apis/texttospeech_v1/classes.rb +28 -27
- data/generated/google/apis/texttospeech_v1beta1.rb +1 -1
- data/generated/google/apis/texttospeech_v1beta1/classes.rb +28 -27
- data/generated/google/apis/toolresults_v1beta3.rb +1 -1
- data/generated/google/apis/toolresults_v1beta3/classes.rb +35 -0
- data/generated/google/apis/toolresults_v1beta3/representations.rb +2 -0
- data/generated/google/apis/tpu_v1.rb +1 -1
- data/generated/google/apis/tpu_v1/classes.rb +17 -88
- data/generated/google/apis/tpu_v1alpha1.rb +1 -1
- data/generated/google/apis/tpu_v1alpha1/classes.rb +17 -88
- data/generated/google/apis/vault_v1.rb +1 -1
- data/generated/google/apis/vault_v1/classes.rb +49 -0
- data/generated/google/apis/vault_v1/representations.rb +18 -0
- data/generated/google/apis/videointelligence_v1.rb +1 -1
- data/generated/google/apis/videointelligence_v1/classes.rb +324 -332
- data/generated/google/apis/videointelligence_v1/representations.rb +102 -0
- data/generated/google/apis/videointelligence_v1/service.rb +217 -9
- data/generated/google/apis/videointelligence_v1beta2.rb +1 -1
- data/generated/google/apis/videointelligence_v1beta2/classes.rb +279 -297
- data/generated/google/apis/videointelligence_v1beta2/representations.rb +102 -0
- data/generated/google/apis/videointelligence_v1p1beta1.rb +1 -1
- data/generated/google/apis/videointelligence_v1p1beta1/classes.rb +324 -332
- data/generated/google/apis/videointelligence_v1p1beta1/representations.rb +102 -0
- data/generated/google/apis/videointelligence_v1p2beta1.rb +1 -1
- data/generated/google/apis/videointelligence_v1p2beta1/classes.rb +324 -332
- data/generated/google/apis/videointelligence_v1p2beta1/representations.rb +102 -0
- data/generated/google/apis/videointelligence_v1p3beta1.rb +1 -1
- data/generated/google/apis/videointelligence_v1p3beta1/classes.rb +324 -332
- data/generated/google/apis/videointelligence_v1p3beta1/representations.rb +102 -0
- data/generated/google/apis/youtube_partner_v1.rb +1 -1
- data/lib/google/apis/version.rb +1 -1
- metadata +6 -2
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://gsuite.google.com/products/cloud-search/
|
27
27
|
module CloudsearchV1
|
28
28
|
VERSION = 'V1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190606'
|
30
30
|
|
31
31
|
# Index and serve your organization's data with Cloud Search
|
32
32
|
AUTH_CLOUD_SEARCH = 'https://www.googleapis.com/auth/cloud_search'
|
@@ -2533,43 +2533,10 @@ module Google
|
|
2533
2533
|
|
2534
2534
|
# The `Status` type defines a logical error model that is suitable for
|
2535
2535
|
# different programming environments, including REST APIs and RPC APIs. It is
|
2536
|
-
# used by [gRPC](https://github.com/grpc).
|
2537
|
-
#
|
2538
|
-
#
|
2539
|
-
#
|
2540
|
-
# The `Status` message contains three pieces of data: error code, error
|
2541
|
-
# message, and error details. The error code should be an enum value of
|
2542
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
2543
|
-
# error message should be a developer-facing English message that helps
|
2544
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
2545
|
-
# error message is needed, put the localized message in the error details or
|
2546
|
-
# localize it in the client. The optional error details may contain arbitrary
|
2547
|
-
# information about the error. There is a predefined set of error detail types
|
2548
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
2549
|
-
# # Language mapping
|
2550
|
-
# The `Status` message is the logical representation of the error model, but it
|
2551
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
2552
|
-
# exposed in different client libraries and different wire protocols, it can be
|
2553
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
2554
|
-
# in Java, but more likely mapped to some error codes in C.
|
2555
|
-
# # Other uses
|
2556
|
-
# The error model and the `Status` message can be used in a variety of
|
2557
|
-
# environments, either with or without APIs, to provide a
|
2558
|
-
# consistent developer experience across different environments.
|
2559
|
-
# Example uses of this error model include:
|
2560
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
2561
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
2562
|
-
# errors.
|
2563
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
2564
|
-
# have a `Status` message for error reporting.
|
2565
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
2566
|
-
# `Status` message should be used directly inside batch response, one for
|
2567
|
-
# each error sub-response.
|
2568
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
2569
|
-
# results in its response, the status of those operations should be
|
2570
|
-
# represented directly using the `Status` message.
|
2571
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
2572
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
2536
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
2537
|
+
# three pieces of data: error code, error message, and error details.
|
2538
|
+
# You can find out more about this error model and how to work with it in the
|
2539
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
2573
2540
|
# Corresponds to the JSON property `error`
|
2574
2541
|
# @return [Google::Apis::CloudsearchV1::Status]
|
2575
2542
|
attr_accessor :error
|
@@ -4346,43 +4313,10 @@ module Google
|
|
4346
4313
|
|
4347
4314
|
# The `Status` type defines a logical error model that is suitable for
|
4348
4315
|
# different programming environments, including REST APIs and RPC APIs. It is
|
4349
|
-
# used by [gRPC](https://github.com/grpc).
|
4350
|
-
#
|
4351
|
-
#
|
4352
|
-
#
|
4353
|
-
# The `Status` message contains three pieces of data: error code, error
|
4354
|
-
# message, and error details. The error code should be an enum value of
|
4355
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
4356
|
-
# error message should be a developer-facing English message that helps
|
4357
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
4358
|
-
# error message is needed, put the localized message in the error details or
|
4359
|
-
# localize it in the client. The optional error details may contain arbitrary
|
4360
|
-
# information about the error. There is a predefined set of error detail types
|
4361
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
4362
|
-
# # Language mapping
|
4363
|
-
# The `Status` message is the logical representation of the error model, but it
|
4364
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
4365
|
-
# exposed in different client libraries and different wire protocols, it can be
|
4366
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
4367
|
-
# in Java, but more likely mapped to some error codes in C.
|
4368
|
-
# # Other uses
|
4369
|
-
# The error model and the `Status` message can be used in a variety of
|
4370
|
-
# environments, either with or without APIs, to provide a
|
4371
|
-
# consistent developer experience across different environments.
|
4372
|
-
# Example uses of this error model include:
|
4373
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
4374
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
4375
|
-
# errors.
|
4376
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
4377
|
-
# have a `Status` message for error reporting.
|
4378
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
4379
|
-
# `Status` message should be used directly inside batch response, one for
|
4380
|
-
# each error sub-response.
|
4381
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
4382
|
-
# results in its response, the status of those operations should be
|
4383
|
-
# represented directly using the `Status` message.
|
4384
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
4385
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
4316
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
4317
|
+
# three pieces of data: error code, error message, and error details.
|
4318
|
+
# You can find out more about this error model and how to work with it in the
|
4319
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
4386
4320
|
class Status
|
4387
4321
|
include Google::Apis::Core::Hashable
|
4388
4322
|
|
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://cloud.google.com/shell/docs/
|
27
27
|
module CloudshellV1
|
28
28
|
VERSION = 'V1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190610'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -170,43 +170,10 @@ module Google
|
|
170
170
|
|
171
171
|
# The `Status` type defines a logical error model that is suitable for
|
172
172
|
# different programming environments, including REST APIs and RPC APIs. It is
|
173
|
-
# used by [gRPC](https://github.com/grpc).
|
174
|
-
#
|
175
|
-
#
|
176
|
-
#
|
177
|
-
# The `Status` message contains three pieces of data: error code, error
|
178
|
-
# message, and error details. The error code should be an enum value of
|
179
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
180
|
-
# error message should be a developer-facing English message that helps
|
181
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
182
|
-
# error message is needed, put the localized message in the error details or
|
183
|
-
# localize it in the client. The optional error details may contain arbitrary
|
184
|
-
# information about the error. There is a predefined set of error detail types
|
185
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
186
|
-
# # Language mapping
|
187
|
-
# The `Status` message is the logical representation of the error model, but it
|
188
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
189
|
-
# exposed in different client libraries and different wire protocols, it can be
|
190
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
191
|
-
# in Java, but more likely mapped to some error codes in C.
|
192
|
-
# # Other uses
|
193
|
-
# The error model and the `Status` message can be used in a variety of
|
194
|
-
# environments, either with or without APIs, to provide a
|
195
|
-
# consistent developer experience across different environments.
|
196
|
-
# Example uses of this error model include:
|
197
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
198
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
199
|
-
# errors.
|
200
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
201
|
-
# have a `Status` message for error reporting.
|
202
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
203
|
-
# `Status` message should be used directly inside batch response, one for
|
204
|
-
# each error sub-response.
|
205
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
206
|
-
# results in its response, the status of those operations should be
|
207
|
-
# represented directly using the `Status` message.
|
208
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
209
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
173
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
174
|
+
# three pieces of data: error code, error message, and error details.
|
175
|
+
# You can find out more about this error model and how to work with it in the
|
176
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
210
177
|
# Corresponds to the JSON property `error`
|
211
178
|
# @return [Google::Apis::CloudshellV1::Status]
|
212
179
|
attr_accessor :error
|
@@ -335,43 +302,10 @@ module Google
|
|
335
302
|
|
336
303
|
# The `Status` type defines a logical error model that is suitable for
|
337
304
|
# different programming environments, including REST APIs and RPC APIs. It is
|
338
|
-
# used by [gRPC](https://github.com/grpc).
|
339
|
-
#
|
340
|
-
#
|
341
|
-
#
|
342
|
-
# The `Status` message contains three pieces of data: error code, error
|
343
|
-
# message, and error details. The error code should be an enum value of
|
344
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
345
|
-
# error message should be a developer-facing English message that helps
|
346
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
347
|
-
# error message is needed, put the localized message in the error details or
|
348
|
-
# localize it in the client. The optional error details may contain arbitrary
|
349
|
-
# information about the error. There is a predefined set of error detail types
|
350
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
351
|
-
# # Language mapping
|
352
|
-
# The `Status` message is the logical representation of the error model, but it
|
353
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
354
|
-
# exposed in different client libraries and different wire protocols, it can be
|
355
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
356
|
-
# in Java, but more likely mapped to some error codes in C.
|
357
|
-
# # Other uses
|
358
|
-
# The error model and the `Status` message can be used in a variety of
|
359
|
-
# environments, either with or without APIs, to provide a
|
360
|
-
# consistent developer experience across different environments.
|
361
|
-
# Example uses of this error model include:
|
362
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
363
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
364
|
-
# errors.
|
365
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
366
|
-
# have a `Status` message for error reporting.
|
367
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
368
|
-
# `Status` message should be used directly inside batch response, one for
|
369
|
-
# each error sub-response.
|
370
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
371
|
-
# results in its response, the status of those operations should be
|
372
|
-
# represented directly using the `Status` message.
|
373
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
374
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
305
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
306
|
+
# three pieces of data: error code, error message, and error details.
|
307
|
+
# You can find out more about this error model and how to work with it in the
|
308
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
375
309
|
class Status
|
376
310
|
include Google::Apis::Core::Hashable
|
377
311
|
|
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://cloud.google.com/shell/docs/
|
27
27
|
module CloudshellV1alpha1
|
28
28
|
VERSION = 'V1alpha1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190610'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -183,43 +183,10 @@ module Google
|
|
183
183
|
|
184
184
|
# The `Status` type defines a logical error model that is suitable for
|
185
185
|
# different programming environments, including REST APIs and RPC APIs. It is
|
186
|
-
# used by [gRPC](https://github.com/grpc).
|
187
|
-
#
|
188
|
-
#
|
189
|
-
#
|
190
|
-
# The `Status` message contains three pieces of data: error code, error
|
191
|
-
# message, and error details. The error code should be an enum value of
|
192
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
193
|
-
# error message should be a developer-facing English message that helps
|
194
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
195
|
-
# error message is needed, put the localized message in the error details or
|
196
|
-
# localize it in the client. The optional error details may contain arbitrary
|
197
|
-
# information about the error. There is a predefined set of error detail types
|
198
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
199
|
-
# # Language mapping
|
200
|
-
# The `Status` message is the logical representation of the error model, but it
|
201
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
202
|
-
# exposed in different client libraries and different wire protocols, it can be
|
203
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
204
|
-
# in Java, but more likely mapped to some error codes in C.
|
205
|
-
# # Other uses
|
206
|
-
# The error model and the `Status` message can be used in a variety of
|
207
|
-
# environments, either with or without APIs, to provide a
|
208
|
-
# consistent developer experience across different environments.
|
209
|
-
# Example uses of this error model include:
|
210
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
211
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
212
|
-
# errors.
|
213
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
214
|
-
# have a `Status` message for error reporting.
|
215
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
216
|
-
# `Status` message should be used directly inside batch response, one for
|
217
|
-
# each error sub-response.
|
218
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
219
|
-
# results in its response, the status of those operations should be
|
220
|
-
# represented directly using the `Status` message.
|
221
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
222
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
186
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
187
|
+
# three pieces of data: error code, error message, and error details.
|
188
|
+
# You can find out more about this error model and how to work with it in the
|
189
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
223
190
|
# Corresponds to the JSON property `error`
|
224
191
|
# @return [Google::Apis::CloudshellV1alpha1::Status]
|
225
192
|
attr_accessor :error
|
@@ -370,43 +337,10 @@ module Google
|
|
370
337
|
|
371
338
|
# The `Status` type defines a logical error model that is suitable for
|
372
339
|
# different programming environments, including REST APIs and RPC APIs. It is
|
373
|
-
# used by [gRPC](https://github.com/grpc).
|
374
|
-
#
|
375
|
-
#
|
376
|
-
#
|
377
|
-
# The `Status` message contains three pieces of data: error code, error
|
378
|
-
# message, and error details. The error code should be an enum value of
|
379
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
380
|
-
# error message should be a developer-facing English message that helps
|
381
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
382
|
-
# error message is needed, put the localized message in the error details or
|
383
|
-
# localize it in the client. The optional error details may contain arbitrary
|
384
|
-
# information about the error. There is a predefined set of error detail types
|
385
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
386
|
-
# # Language mapping
|
387
|
-
# The `Status` message is the logical representation of the error model, but it
|
388
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
389
|
-
# exposed in different client libraries and different wire protocols, it can be
|
390
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
391
|
-
# in Java, but more likely mapped to some error codes in C.
|
392
|
-
# # Other uses
|
393
|
-
# The error model and the `Status` message can be used in a variety of
|
394
|
-
# environments, either with or without APIs, to provide a
|
395
|
-
# consistent developer experience across different environments.
|
396
|
-
# Example uses of this error model include:
|
397
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
398
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
399
|
-
# errors.
|
400
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
401
|
-
# have a `Status` message for error reporting.
|
402
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
403
|
-
# `Status` message should be used directly inside batch response, one for
|
404
|
-
# each error sub-response.
|
405
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
406
|
-
# results in its response, the status of those operations should be
|
407
|
-
# represented directly using the `Status` message.
|
408
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
409
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
340
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
341
|
+
# three pieces of data: error code, error message, and error details.
|
342
|
+
# You can find out more about this error model and how to work with it in the
|
343
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
410
344
|
class Status
|
411
345
|
include Google::Apis::Core::Hashable
|
412
346
|
|
@@ -25,7 +25,7 @@ module Google
|
|
25
25
|
# @see https://cloud.google.com/tasks/
|
26
26
|
module CloudtasksV2beta2
|
27
27
|
VERSION = 'V2beta2'
|
28
|
-
REVISION = '
|
28
|
+
REVISION = '20190618'
|
29
29
|
|
30
30
|
# View and manage your data across Google Cloud Platform services
|
31
31
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -668,6 +668,14 @@ module Google
|
|
668
668
|
# @return [String]
|
669
669
|
attr_accessor :filter
|
670
670
|
|
671
|
+
# Required.
|
672
|
+
# The duration of the lease.
|
673
|
+
# Each task returned in the response will
|
674
|
+
# have its schedule_time set to the current
|
675
|
+
# time plus the `lease_duration`. The task is leased until its
|
676
|
+
# schedule_time; thus, the task will not be
|
677
|
+
# returned to another LeaseTasks call
|
678
|
+
# before its schedule_time.
|
671
679
|
# After the worker has successfully finished the work associated
|
672
680
|
# with the task, the worker must call via
|
673
681
|
# AcknowledgeTask before the
|
@@ -29,7 +29,7 @@ module Google
|
|
29
29
|
# @see https://cloud.google.com/trace
|
30
30
|
module CloudtraceV2
|
31
31
|
VERSION = 'V2'
|
32
|
-
REVISION = '
|
32
|
+
REVISION = '20190605'
|
33
33
|
|
34
34
|
# View and manage your data across Google Cloud Platform services
|
35
35
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -366,43 +366,10 @@ module Google
|
|
366
366
|
|
367
367
|
# The `Status` type defines a logical error model that is suitable for
|
368
368
|
# different programming environments, including REST APIs and RPC APIs. It is
|
369
|
-
# used by [gRPC](https://github.com/grpc).
|
370
|
-
#
|
371
|
-
#
|
372
|
-
#
|
373
|
-
# The `Status` message contains three pieces of data: error code, error
|
374
|
-
# message, and error details. The error code should be an enum value of
|
375
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
376
|
-
# error message should be a developer-facing English message that helps
|
377
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
378
|
-
# error message is needed, put the localized message in the error details or
|
379
|
-
# localize it in the client. The optional error details may contain arbitrary
|
380
|
-
# information about the error. There is a predefined set of error detail types
|
381
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
382
|
-
# # Language mapping
|
383
|
-
# The `Status` message is the logical representation of the error model, but it
|
384
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
385
|
-
# exposed in different client libraries and different wire protocols, it can be
|
386
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
387
|
-
# in Java, but more likely mapped to some error codes in C.
|
388
|
-
# # Other uses
|
389
|
-
# The error model and the `Status` message can be used in a variety of
|
390
|
-
# environments, either with or without APIs, to provide a
|
391
|
-
# consistent developer experience across different environments.
|
392
|
-
# Example uses of this error model include:
|
393
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
394
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
395
|
-
# errors.
|
396
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
397
|
-
# have a `Status` message for error reporting.
|
398
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
399
|
-
# `Status` message should be used directly inside batch response, one for
|
400
|
-
# each error sub-response.
|
401
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
402
|
-
# results in its response, the status of those operations should be
|
403
|
-
# represented directly using the `Status` message.
|
404
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
405
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
369
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
370
|
+
# three pieces of data: error code, error message, and error details.
|
371
|
+
# You can find out more about this error model and how to work with it in the
|
372
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
406
373
|
# Corresponds to the JSON property `status`
|
407
374
|
# @return [Google::Apis::CloudtraceV2::Status]
|
408
375
|
attr_accessor :status
|
@@ -552,43 +519,10 @@ module Google
|
|
552
519
|
|
553
520
|
# The `Status` type defines a logical error model that is suitable for
|
554
521
|
# different programming environments, including REST APIs and RPC APIs. It is
|
555
|
-
# used by [gRPC](https://github.com/grpc).
|
556
|
-
#
|
557
|
-
#
|
558
|
-
#
|
559
|
-
# The `Status` message contains three pieces of data: error code, error
|
560
|
-
# message, and error details. The error code should be an enum value of
|
561
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
562
|
-
# error message should be a developer-facing English message that helps
|
563
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
564
|
-
# error message is needed, put the localized message in the error details or
|
565
|
-
# localize it in the client. The optional error details may contain arbitrary
|
566
|
-
# information about the error. There is a predefined set of error detail types
|
567
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
568
|
-
# # Language mapping
|
569
|
-
# The `Status` message is the logical representation of the error model, but it
|
570
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
571
|
-
# exposed in different client libraries and different wire protocols, it can be
|
572
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
573
|
-
# in Java, but more likely mapped to some error codes in C.
|
574
|
-
# # Other uses
|
575
|
-
# The error model and the `Status` message can be used in a variety of
|
576
|
-
# environments, either with or without APIs, to provide a
|
577
|
-
# consistent developer experience across different environments.
|
578
|
-
# Example uses of this error model include:
|
579
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
580
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
581
|
-
# errors.
|
582
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
583
|
-
# have a `Status` message for error reporting.
|
584
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
585
|
-
# `Status` message should be used directly inside batch response, one for
|
586
|
-
# each error sub-response.
|
587
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
588
|
-
# results in its response, the status of those operations should be
|
589
|
-
# represented directly using the `Status` message.
|
590
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
591
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
522
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
523
|
+
# three pieces of data: error code, error message, and error details.
|
524
|
+
# You can find out more about this error model and how to work with it in the
|
525
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
592
526
|
class Status
|
593
527
|
include Google::Apis::Core::Hashable
|
594
528
|
|
@@ -27,10 +27,10 @@ module Google
|
|
27
27
|
# doNotStore" flag to ensure that all submitted comments are automatically
|
28
28
|
# deleted after scores are returned.
|
29
29
|
#
|
30
|
-
# @see https://
|
30
|
+
# @see https://github.com/conversationai/perspectiveapi/blob/master/README.md
|
31
31
|
module CommentanalyzerV1alpha1
|
32
32
|
VERSION = 'V1alpha1'
|
33
|
-
REVISION = '
|
33
|
+
REVISION = '20190616'
|
34
34
|
|
35
35
|
# View your email address
|
36
36
|
AUTH_USERINFO_EMAIL = 'https://www.googleapis.com/auth/userinfo.email'
|