google-cloud-asset-v1 0.4.3 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,185 @@
1
+ # frozen_string_literal: true
2
+
3
+ # Copyright 2020 Google LLC
4
+ #
5
+ # Licensed under the Apache License, Version 2.0 (the "License");
6
+ # you may not use this file except in compliance with the License.
7
+ # You may obtain a copy of the License at
8
+ #
9
+ # https://www.apache.org/licenses/LICENSE-2.0
10
+ #
11
+ # Unless required by applicable law or agreed to in writing, software
12
+ # distributed under the License is distributed on an "AS IS" BASIS,
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14
+ # See the License for the specific language governing permissions and
15
+ # limitations under the License.
16
+
17
+ # Auto-generated by gapic-generator-ruby. DO NOT EDIT!
18
+
19
+
20
+ module Google
21
+ module Rpc
22
+ # The canonical error codes for gRPC APIs.
23
+ #
24
+ #
25
+ # Sometimes multiple error codes may apply. Services should return
26
+ # the most specific error code that applies. For example, prefer
27
+ # `OUT_OF_RANGE` over `FAILED_PRECONDITION` if both codes apply.
28
+ # Similarly prefer `NOT_FOUND` or `ALREADY_EXISTS` over `FAILED_PRECONDITION`.
29
+ module Code
30
+ # Not an error; returned on success
31
+ #
32
+ # HTTP Mapping: 200 OK
33
+ OK = 0
34
+
35
+ # The operation was cancelled, typically by the caller.
36
+ #
37
+ # HTTP Mapping: 499 Client Closed Request
38
+ CANCELLED = 1
39
+
40
+ # Unknown error. For example, this error may be returned when
41
+ # a `Status` value received from another address space belongs to
42
+ # an error space that is not known in this address space. Also
43
+ # errors raised by APIs that do not return enough error information
44
+ # may be converted to this error.
45
+ #
46
+ # HTTP Mapping: 500 Internal Server Error
47
+ UNKNOWN = 2
48
+
49
+ # The client specified an invalid argument. Note that this differs
50
+ # from `FAILED_PRECONDITION`. `INVALID_ARGUMENT` indicates arguments
51
+ # that are problematic regardless of the state of the system
52
+ # (e.g., a malformed file name).
53
+ #
54
+ # HTTP Mapping: 400 Bad Request
55
+ INVALID_ARGUMENT = 3
56
+
57
+ # The deadline expired before the operation could complete. For operations
58
+ # that change the state of the system, this error may be returned
59
+ # even if the operation has completed successfully. For example, a
60
+ # successful response from a server could have been delayed long
61
+ # enough for the deadline to expire.
62
+ #
63
+ # HTTP Mapping: 504 Gateway Timeout
64
+ DEADLINE_EXCEEDED = 4
65
+
66
+ # Some requested entity (e.g., file or directory) was not found.
67
+ #
68
+ # Note to server developers: if a request is denied for an entire class
69
+ # of users, such as gradual feature rollout or undocumented whitelist,
70
+ # `NOT_FOUND` may be used. If a request is denied for some users within
71
+ # a class of users, such as user-based access control, `PERMISSION_DENIED`
72
+ # must be used.
73
+ #
74
+ # HTTP Mapping: 404 Not Found
75
+ NOT_FOUND = 5
76
+
77
+ # The entity that a client attempted to create (e.g., file or directory)
78
+ # already exists.
79
+ #
80
+ # HTTP Mapping: 409 Conflict
81
+ ALREADY_EXISTS = 6
82
+
83
+ # The caller does not have permission to execute the specified
84
+ # operation. `PERMISSION_DENIED` must not be used for rejections
85
+ # caused by exhausting some resource (use `RESOURCE_EXHAUSTED`
86
+ # instead for those errors). `PERMISSION_DENIED` must not be
87
+ # used if the caller can not be identified (use `UNAUTHENTICATED`
88
+ # instead for those errors). This error code does not imply the
89
+ # request is valid or the requested entity exists or satisfies
90
+ # other pre-conditions.
91
+ #
92
+ # HTTP Mapping: 403 Forbidden
93
+ PERMISSION_DENIED = 7
94
+
95
+ # The request does not have valid authentication credentials for the
96
+ # operation.
97
+ #
98
+ # HTTP Mapping: 401 Unauthorized
99
+ UNAUTHENTICATED = 16
100
+
101
+ # Some resource has been exhausted, perhaps a per-user quota, or
102
+ # perhaps the entire file system is out of space.
103
+ #
104
+ # HTTP Mapping: 429 Too Many Requests
105
+ RESOURCE_EXHAUSTED = 8
106
+
107
+ # The operation was rejected because the system is not in a state
108
+ # required for the operation's execution. For example, the directory
109
+ # to be deleted is non-empty, an rmdir operation is applied to
110
+ # a non-directory, etc.
111
+ #
112
+ # Service implementors can use the following guidelines to decide
113
+ # between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`:
114
+ # (a) Use `UNAVAILABLE` if the client can retry just the failing call.
115
+ # (b) Use `ABORTED` if the client should retry at a higher level
116
+ # (e.g., when a client-specified test-and-set fails, indicating the
117
+ # client should restart a read-modify-write sequence).
118
+ # (c) Use `FAILED_PRECONDITION` if the client should not retry until
119
+ # the system state has been explicitly fixed. E.g., if an "rmdir"
120
+ # fails because the directory is non-empty, `FAILED_PRECONDITION`
121
+ # should be returned since the client should not retry unless
122
+ # the files are deleted from the directory.
123
+ #
124
+ # HTTP Mapping: 400 Bad Request
125
+ FAILED_PRECONDITION = 9
126
+
127
+ # The operation was aborted, typically due to a concurrency issue such as
128
+ # a sequencer check failure or transaction abort.
129
+ #
130
+ # See the guidelines above for deciding between `FAILED_PRECONDITION`,
131
+ # `ABORTED`, and `UNAVAILABLE`.
132
+ #
133
+ # HTTP Mapping: 409 Conflict
134
+ ABORTED = 10
135
+
136
+ # The operation was attempted past the valid range. E.g., seeking or
137
+ # reading past end-of-file.
138
+ #
139
+ # Unlike `INVALID_ARGUMENT`, this error indicates a problem that may
140
+ # be fixed if the system state changes. For example, a 32-bit file
141
+ # system will generate `INVALID_ARGUMENT` if asked to read at an
142
+ # offset that is not in the range [0,2^32-1], but it will generate
143
+ # `OUT_OF_RANGE` if asked to read from an offset past the current
144
+ # file size.
145
+ #
146
+ # There is a fair bit of overlap between `FAILED_PRECONDITION` and
147
+ # `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific
148
+ # error) when it applies so that callers who are iterating through
149
+ # a space can easily look for an `OUT_OF_RANGE` error to detect when
150
+ # they are done.
151
+ #
152
+ # HTTP Mapping: 400 Bad Request
153
+ OUT_OF_RANGE = 11
154
+
155
+ # The operation is not implemented or is not supported/enabled in this
156
+ # service.
157
+ #
158
+ # HTTP Mapping: 501 Not Implemented
159
+ UNIMPLEMENTED = 12
160
+
161
+ # Internal errors. This means that some invariants expected by the
162
+ # underlying system have been broken. This error code is reserved
163
+ # for serious errors.
164
+ #
165
+ # HTTP Mapping: 500 Internal Server Error
166
+ INTERNAL = 13
167
+
168
+ # The service is currently unavailable. This is most likely a
169
+ # transient condition, which can be corrected by retrying with
170
+ # a backoff. Note that it is not always safe to retry
171
+ # non-idempotent operations.
172
+ #
173
+ # See the guidelines above for deciding between `FAILED_PRECONDITION`,
174
+ # `ABORTED`, and `UNAVAILABLE`.
175
+ #
176
+ # HTTP Mapping: 503 Service Unavailable
177
+ UNAVAILABLE = 14
178
+
179
+ # Unrecoverable data loss or corruption.
180
+ #
181
+ # HTTP Mapping: 500 Internal Server Error
182
+ DATA_LOSS = 15
183
+ end
184
+ end
185
+ end
@@ -28,7 +28,7 @@ module Google
28
28
  # [API Design Guide](https://cloud.google.com/apis/design/errors).
29
29
  # @!attribute [rw] code
30
30
  # @return [::Integer]
31
- # The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
31
+ # The status code, which should be an enum value of {::Google::Rpc::Code google.rpc.Code}.
32
32
  # @!attribute [rw] message
33
33
  # @return [::String]
34
34
  # A developer-facing error message, which should be in English. Any
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-cloud-asset-v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.4.3
4
+ version: 0.6.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-06-06 00:00:00.000000000 Z
11
+ date: 2020-09-03 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: gapic-common
@@ -16,14 +16,14 @@ dependencies:
16
16
  requirements:
17
17
  - - "~>"
18
18
  - !ruby/object:Gem::Version
19
- version: '0.2'
19
+ version: '0.3'
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - "~>"
25
25
  - !ruby/object:Gem::Version
26
- version: '0.2'
26
+ version: '0.3'
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: google-cloud-errors
29
29
  requirement: !ruby/object:Gem::Requirement
@@ -211,10 +211,12 @@ files:
211
211
  - proto_docs/google/identity/accesscontextmanager/v1/service_perimeter.rb
212
212
  - proto_docs/google/longrunning/operations.rb
213
213
  - proto_docs/google/protobuf/any.rb
214
+ - proto_docs/google/protobuf/duration.rb
214
215
  - proto_docs/google/protobuf/empty.rb
215
216
  - proto_docs/google/protobuf/field_mask.rb
216
217
  - proto_docs/google/protobuf/struct.rb
217
218
  - proto_docs/google/protobuf/timestamp.rb
219
+ - proto_docs/google/rpc/code.rb
218
220
  - proto_docs/google/rpc/status.rb
219
221
  - proto_docs/google/type/expr.rb
220
222
  homepage: https://github.com/googleapis/google-cloud-ruby