google-cloud-scheduler 1.2.0 → 1.2.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/google/cloud/scheduler.rb +1 -1
- data/lib/google/cloud/scheduler/v1.rb +1 -1
- data/lib/google/cloud/scheduler/v1/cloud_scheduler_client.rb +1 -1
- data/lib/google/cloud/scheduler/v1/credentials.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/cloud/scheduler/v1/cloudscheduler.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/cloud/scheduler/v1/job.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/cloud/scheduler/v1/target.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/protobuf/any.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/protobuf/duration.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/protobuf/empty.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/protobuf/field_mask.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/protobuf/timestamp.rb +1 -1
- data/lib/google/cloud/scheduler/v1/doc/google/rpc/status.rb +7 -55
- data/lib/google/cloud/scheduler/v1beta1.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/cloud_scheduler_client.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/credentials.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/cloud/scheduler/v1beta1/cloudscheduler.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/cloud/scheduler/v1beta1/job.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/cloud/scheduler/v1beta1/target.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/protobuf/any.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/protobuf/duration.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/protobuf/empty.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/protobuf/field_mask.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/protobuf/timestamp.rb +1 -1
- data/lib/google/cloud/scheduler/v1beta1/doc/google/rpc/status.rb +7 -55
- data/lib/google/cloud/scheduler/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fca9c8a6d5d911b33c6c10f4fde58985c2a747b41f1b8317546a150ceab37154
|
|
4
|
+
data.tar.gz: 216dc757a48d83e9ab9020fdf9c109b5dae2d21539d491fc8a435e0df3838475
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: fe388a3bbc01796813eb46bdbdd7b92321f6c9dff38631a7cf3581e14a58aa33ee748184c4f226735239be7c904b76cc121db5fc0bdd9b160dcd8af2388678b6
|
|
7
|
+
data.tar.gz: 540ab31d23f50f30207b6d266a709a58a157a076a68b0de5446aae656d111d2350afdad0a484ab81bceaa91f7396556f93344350e9e869133987be575b474a35
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Copyright
|
|
1
|
+
# Copyright 2020 Google LLC
|
|
2
2
|
#
|
|
3
3
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
4
4
|
# you may not use this file except in compliance with the License.
|
|
@@ -17,67 +17,19 @@ module Google
|
|
|
17
17
|
module Rpc
|
|
18
18
|
# The `Status` type defines a logical error model that is suitable for
|
|
19
19
|
# different programming environments, including REST APIs and RPC APIs. It is
|
|
20
|
-
# used by [gRPC](https://github.com/grpc).
|
|
20
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
|
21
|
+
# three pieces of data: error code, error message, and error details.
|
|
21
22
|
#
|
|
22
|
-
#
|
|
23
|
-
#
|
|
24
|
-
#
|
|
25
|
-
# = Overview
|
|
26
|
-
#
|
|
27
|
-
# The `Status` message contains three pieces of data: error code, error
|
|
28
|
-
# message, and error details. The error code should be an enum value of
|
|
29
|
-
# {Google::Rpc::Code}, but it may accept additional error codes
|
|
30
|
-
# if needed. The error message should be a developer-facing English message
|
|
31
|
-
# that helps developers *understand* and *resolve* the error. If a localized
|
|
32
|
-
# user-facing error message is needed, put the localized message in the error
|
|
33
|
-
# details or localize it in the client. The optional error details may contain
|
|
34
|
-
# arbitrary information about the error. There is a predefined set of error
|
|
35
|
-
# detail types in the package `google.rpc` that can be used for common error
|
|
36
|
-
# conditions.
|
|
37
|
-
#
|
|
38
|
-
# = Language mapping
|
|
39
|
-
#
|
|
40
|
-
# The `Status` message is the logical representation of the error model, but it
|
|
41
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
|
42
|
-
# exposed in different client libraries and different wire protocols, it can be
|
|
43
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
|
44
|
-
# in Java, but more likely mapped to some error codes in C.
|
|
45
|
-
#
|
|
46
|
-
# = Other uses
|
|
47
|
-
#
|
|
48
|
-
# The error model and the `Status` message can be used in a variety of
|
|
49
|
-
# environments, either with or without APIs, to provide a
|
|
50
|
-
# consistent developer experience across different environments.
|
|
51
|
-
#
|
|
52
|
-
# Example uses of this error model include:
|
|
53
|
-
#
|
|
54
|
-
# * Partial errors. If a service needs to return partial errors to the client,
|
|
55
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
|
56
|
-
# errors.
|
|
57
|
-
#
|
|
58
|
-
# * Workflow errors. A typical workflow has multiple steps. Each step may
|
|
59
|
-
# have a `Status` message for error reporting.
|
|
60
|
-
#
|
|
61
|
-
# * Batch operations. If a client uses batch request and batch response, the
|
|
62
|
-
# `Status` message should be used directly inside batch response, one for
|
|
63
|
-
# each error sub-response.
|
|
64
|
-
#
|
|
65
|
-
# * Asynchronous operations. If an API call embeds asynchronous operation
|
|
66
|
-
# results in its response, the status of those operations should be
|
|
67
|
-
# represented directly using the `Status` message.
|
|
68
|
-
#
|
|
69
|
-
# * Logging. If some API errors are stored in logs, the message `Status` could
|
|
70
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
|
23
|
+
# You can find out more about this error model and how to work with it in the
|
|
24
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
|
71
25
|
# @!attribute [rw] code
|
|
72
26
|
# @return [Integer]
|
|
73
|
-
# The status code, which should be an enum value of
|
|
74
|
-
# {Google::Rpc::Code}.
|
|
27
|
+
# The status code, which should be an enum value of {Google::Rpc::Code}.
|
|
75
28
|
# @!attribute [rw] message
|
|
76
29
|
# @return [String]
|
|
77
30
|
# A developer-facing error message, which should be in English. Any
|
|
78
31
|
# user-facing error message should be localized and sent in the
|
|
79
|
-
# {Google::Rpc::Status#details} field, or localized
|
|
80
|
-
# by the client.
|
|
32
|
+
# {Google::Rpc::Status#details} field, or localized by the client.
|
|
81
33
|
# @!attribute [rw] details
|
|
82
34
|
# @return [Array<Google::Protobuf::Any>]
|
|
83
35
|
# A list of messages that carry the error details. There is a common set of
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Copyright
|
|
1
|
+
# Copyright 2020 Google LLC
|
|
2
2
|
#
|
|
3
3
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
4
4
|
# you may not use this file except in compliance with the License.
|
|
@@ -17,67 +17,19 @@ module Google
|
|
|
17
17
|
module Rpc
|
|
18
18
|
# The `Status` type defines a logical error model that is suitable for
|
|
19
19
|
# different programming environments, including REST APIs and RPC APIs. It is
|
|
20
|
-
# used by [gRPC](https://github.com/grpc).
|
|
20
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
|
21
|
+
# three pieces of data: error code, error message, and error details.
|
|
21
22
|
#
|
|
22
|
-
#
|
|
23
|
-
#
|
|
24
|
-
#
|
|
25
|
-
# = Overview
|
|
26
|
-
#
|
|
27
|
-
# The `Status` message contains three pieces of data: error code, error
|
|
28
|
-
# message, and error details. The error code should be an enum value of
|
|
29
|
-
# {Google::Rpc::Code}, but it may accept additional error codes
|
|
30
|
-
# if needed. The error message should be a developer-facing English message
|
|
31
|
-
# that helps developers *understand* and *resolve* the error. If a localized
|
|
32
|
-
# user-facing error message is needed, put the localized message in the error
|
|
33
|
-
# details or localize it in the client. The optional error details may contain
|
|
34
|
-
# arbitrary information about the error. There is a predefined set of error
|
|
35
|
-
# detail types in the package `google.rpc` that can be used for common error
|
|
36
|
-
# conditions.
|
|
37
|
-
#
|
|
38
|
-
# = Language mapping
|
|
39
|
-
#
|
|
40
|
-
# The `Status` message is the logical representation of the error model, but it
|
|
41
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
|
42
|
-
# exposed in different client libraries and different wire protocols, it can be
|
|
43
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
|
44
|
-
# in Java, but more likely mapped to some error codes in C.
|
|
45
|
-
#
|
|
46
|
-
# = Other uses
|
|
47
|
-
#
|
|
48
|
-
# The error model and the `Status` message can be used in a variety of
|
|
49
|
-
# environments, either with or without APIs, to provide a
|
|
50
|
-
# consistent developer experience across different environments.
|
|
51
|
-
#
|
|
52
|
-
# Example uses of this error model include:
|
|
53
|
-
#
|
|
54
|
-
# * Partial errors. If a service needs to return partial errors to the client,
|
|
55
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
|
56
|
-
# errors.
|
|
57
|
-
#
|
|
58
|
-
# * Workflow errors. A typical workflow has multiple steps. Each step may
|
|
59
|
-
# have a `Status` message for error reporting.
|
|
60
|
-
#
|
|
61
|
-
# * Batch operations. If a client uses batch request and batch response, the
|
|
62
|
-
# `Status` message should be used directly inside batch response, one for
|
|
63
|
-
# each error sub-response.
|
|
64
|
-
#
|
|
65
|
-
# * Asynchronous operations. If an API call embeds asynchronous operation
|
|
66
|
-
# results in its response, the status of those operations should be
|
|
67
|
-
# represented directly using the `Status` message.
|
|
68
|
-
#
|
|
69
|
-
# * Logging. If some API errors are stored in logs, the message `Status` could
|
|
70
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
|
23
|
+
# You can find out more about this error model and how to work with it in the
|
|
24
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
|
71
25
|
# @!attribute [rw] code
|
|
72
26
|
# @return [Integer]
|
|
73
|
-
# The status code, which should be an enum value of
|
|
74
|
-
# {Google::Rpc::Code}.
|
|
27
|
+
# The status code, which should be an enum value of {Google::Rpc::Code}.
|
|
75
28
|
# @!attribute [rw] message
|
|
76
29
|
# @return [String]
|
|
77
30
|
# A developer-facing error message, which should be in English. Any
|
|
78
31
|
# user-facing error message should be localized and sent in the
|
|
79
|
-
# {Google::Rpc::Status#details} field, or localized
|
|
80
|
-
# by the client.
|
|
32
|
+
# {Google::Rpc::Status#details} field, or localized by the client.
|
|
81
33
|
# @!attribute [rw] details
|
|
82
34
|
# @return [Array<Google::Protobuf::Any>]
|
|
83
35
|
# A list of messages that carry the error details. There is a common set of
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: google-cloud-scheduler
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.2.
|
|
4
|
+
version: 1.2.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Google LLC
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2020-01-23 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: google-gax
|