-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The transitive dependency tree for the grpc-go protos is quite substantial - and since we only need the proto definitions to generate JSON, we don't require interoperability with the canonical package paths. This change removes the transitive dependencies on: - buf.build/cnfc/xds - buf.build/envoyproxy/envoy - buf.build/googleapis/googleapis - buf.build/grpc/grpc - buf.build/opencensus/opencensus - buf.build/opentelemetry/opentelemetry - buf.build/prometheus/client-model
- Loading branch information
Showing
5 changed files
with
880 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,35 +1,2 @@ | ||
| # Generated by buf. DO NOT EDIT. | ||
| version: v1 | ||
| deps: | ||
| - remote: buf.build | ||
| owner: cncf | ||
| repository: xds | ||
| commit: f6f9b109ae2f445e9c1c00bb765b5373 | ||
| - remote: buf.build | ||
| owner: envoyproxy | ||
| repository: envoy | ||
| commit: 3b42f172a19b4a138a32f55dc9867ca7 | ||
| - remote: buf.build | ||
| owner: envoyproxy | ||
| repository: protoc-gen-validate | ||
| commit: 45685e052c7e406b9fbd441fc7a568a5 | ||
| - remote: buf.build | ||
| owner: googleapis | ||
| repository: googleapis | ||
| commit: 62f35d8aed1149c291d606d958a7ce32 | ||
| - remote: buf.build | ||
| owner: grpc | ||
| repository: grpc | ||
| commit: 428bdb303f1c4bb9b33364ed61df516a | ||
| - remote: buf.build | ||
| owner: opencensus | ||
| repository: opencensus | ||
| commit: d1d7ccd1281e4f42ab7ce9a7d2b29e33 | ||
| - remote: buf.build | ||
| owner: opentelemetry | ||
| repository: opentelemetry | ||
| commit: 038316eb65414db8bb0cd88c47a4ee0f | ||
| - remote: buf.build | ||
| owner: prometheus | ||
| repository: client-model | ||
| commit: 1d56a02d481a412a83b3c4984eb90c2e |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,180 @@ | ||
| // Copyright 2020 Google LLC | ||
| // | ||
| // Licensed under the Apache License, Version 2.0 (the "License"); | ||
| // you may not use this file except in compliance with the License. | ||
| // You may obtain a copy of the License at | ||
| // | ||
| // http://www.apache.org/licenses/LICENSE-2.0 | ||
| // | ||
| // Unless required by applicable law or agreed to in writing, software | ||
| // distributed under the License is distributed on an "AS IS" BASIS, | ||
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| // See the License for the specific language governing permissions and | ||
| // limitations under the License. | ||
|
|
||
| syntax = "proto3"; | ||
|
|
||
| package einride.serviceconfig.v1; | ||
|
|
||
| // The canonical error codes for gRPC APIs. | ||
| // | ||
| // | ||
| // Sometimes multiple error codes may apply. Services should return | ||
| // the most specific error code that applies. For example, prefer | ||
| // `OUT_OF_RANGE` over `FAILED_PRECONDITION` if both codes apply. | ||
| // Similarly prefer `NOT_FOUND` or `ALREADY_EXISTS` over `FAILED_PRECONDITION`. | ||
| enum Code { | ||
| // Not an error; returned on success | ||
| // | ||
| // HTTP Mapping: 200 OK | ||
| OK = 0; | ||
|
|
||
| // The operation was cancelled, typically by the caller. | ||
| // | ||
| // HTTP Mapping: 499 Client Closed Request | ||
| CANCELLED = 1; | ||
|
|
||
| // Unknown error. For example, this error may be returned when | ||
| // a `Status` value received from another address space belongs to | ||
| // an error space that is not known in this address space. Also | ||
| // errors raised by APIs that do not return enough error information | ||
| // may be converted to this error. | ||
| // | ||
| // HTTP Mapping: 500 Internal Server Error | ||
| UNKNOWN = 2; | ||
|
|
||
| // The client specified an invalid argument. Note that this differs | ||
| // from `FAILED_PRECONDITION`. `INVALID_ARGUMENT` indicates arguments | ||
| // that are problematic regardless of the state of the system | ||
| // (e.g., a malformed file name). | ||
| // | ||
| // HTTP Mapping: 400 Bad Request | ||
| INVALID_ARGUMENT = 3; | ||
|
|
||
| // The deadline expired before the operation could complete. For operations | ||
| // that change the state of the system, this error may be returned | ||
| // even if the operation has completed successfully. For example, a | ||
| // successful response from a server could have been delayed long | ||
| // enough for the deadline to expire. | ||
| // | ||
| // HTTP Mapping: 504 Gateway Timeout | ||
| DEADLINE_EXCEEDED = 4; | ||
|
|
||
| // Some requested entity (e.g., file or directory) was not found. | ||
| // | ||
| // Note to server developers: if a request is denied for an entire class | ||
| // of users, such as gradual feature rollout or undocumented whitelist, | ||
| // `NOT_FOUND` may be used. If a request is denied for some users within | ||
| // a class of users, such as user-based access control, `PERMISSION_DENIED` | ||
| // must be used. | ||
| // | ||
| // HTTP Mapping: 404 Not Found | ||
| NOT_FOUND = 5; | ||
|
|
||
| // The entity that a client attempted to create (e.g., file or directory) | ||
| // already exists. | ||
| // | ||
| // HTTP Mapping: 409 Conflict | ||
| ALREADY_EXISTS = 6; | ||
|
|
||
| // The caller does not have permission to execute the specified | ||
| // operation. `PERMISSION_DENIED` must not be used for rejections | ||
| // caused by exhausting some resource (use `RESOURCE_EXHAUSTED` | ||
| // instead for those errors). `PERMISSION_DENIED` must not be | ||
| // used if the caller can not be identified (use `UNAUTHENTICATED` | ||
| // instead for those errors). This error code does not imply the | ||
| // request is valid or the requested entity exists or satisfies | ||
| // other pre-conditions. | ||
| // | ||
| // HTTP Mapping: 403 Forbidden | ||
| PERMISSION_DENIED = 7; | ||
|
|
||
| // The request does not have valid authentication credentials for the | ||
| // operation. | ||
| // | ||
| // HTTP Mapping: 401 Unauthorized | ||
| UNAUTHENTICATED = 16; | ||
|
|
||
| // Some resource has been exhausted, perhaps a per-user quota, or | ||
| // perhaps the entire file system is out of space. | ||
| // | ||
| // HTTP Mapping: 429 Too Many Requests | ||
| RESOURCE_EXHAUSTED = 8; | ||
|
|
||
| // The operation was rejected because the system is not in a state | ||
| // required for the operation's execution. For example, the directory | ||
| // to be deleted is non-empty, an rmdir operation is applied to | ||
| // a non-directory, etc. | ||
| // | ||
| // Service implementors can use the following guidelines to decide | ||
| // between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: | ||
| // (a) Use `UNAVAILABLE` if the client can retry just the failing call. | ||
| // (b) Use `ABORTED` if the client should retry at a higher level | ||
| // (e.g., when a client-specified test-and-set fails, indicating the | ||
| // client should restart a read-modify-write sequence). | ||
| // (c) Use `FAILED_PRECONDITION` if the client should not retry until | ||
| // the system state has been explicitly fixed. E.g., if an "rmdir" | ||
| // fails because the directory is non-empty, `FAILED_PRECONDITION` | ||
| // should be returned since the client should not retry unless | ||
| // the files are deleted from the directory. | ||
| // | ||
| // HTTP Mapping: 400 Bad Request | ||
| FAILED_PRECONDITION = 9; | ||
|
|
||
| // The operation was aborted, typically due to a concurrency issue such as | ||
| // a sequencer check failure or transaction abort. | ||
| // | ||
| // See the guidelines above for deciding between `FAILED_PRECONDITION`, | ||
| // `ABORTED`, and `UNAVAILABLE`. | ||
| // | ||
| // HTTP Mapping: 409 Conflict | ||
| ABORTED = 10; | ||
|
|
||
| // The operation was attempted past the valid range. E.g., seeking or | ||
| // reading past end-of-file. | ||
| // | ||
| // Unlike `INVALID_ARGUMENT`, this error indicates a problem that may | ||
| // be fixed if the system state changes. For example, a 32-bit file | ||
| // system will generate `INVALID_ARGUMENT` if asked to read at an | ||
| // offset that is not in the range [0,2^32-1], but it will generate | ||
| // `OUT_OF_RANGE` if asked to read from an offset past the current | ||
| // file size. | ||
| // | ||
| // There is a fair bit of overlap between `FAILED_PRECONDITION` and | ||
| // `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific | ||
| // error) when it applies so that callers who are iterating through | ||
| // a space can easily look for an `OUT_OF_RANGE` error to detect when | ||
| // they are done. | ||
| // | ||
| // HTTP Mapping: 400 Bad Request | ||
| OUT_OF_RANGE = 11; | ||
|
|
||
| // The operation is not implemented or is not supported/enabled in this | ||
| // service. | ||
| // | ||
| // HTTP Mapping: 501 Not Implemented | ||
| UNIMPLEMENTED = 12; | ||
|
|
||
| // Internal errors. This means that some invariants expected by the | ||
| // underlying system have been broken. This error code is reserved | ||
| // for serious errors. | ||
| // | ||
| // HTTP Mapping: 500 Internal Server Error | ||
| INTERNAL = 13; | ||
|
|
||
| // The service is currently unavailable. This is most likely a | ||
| // transient condition, which can be corrected by retrying with | ||
| // a backoff. Note that it is not always safe to retry | ||
| // non-idempotent operations. | ||
| // | ||
| // See the guidelines above for deciding between `FAILED_PRECONDITION`, | ||
| // `ABORTED`, and `UNAVAILABLE`. | ||
| // | ||
| // HTTP Mapping: 503 Service Unavailable | ||
| UNAVAILABLE = 14; | ||
|
|
||
| // Unrecoverable data loss or corruption. | ||
| // | ||
| // HTTP Mapping: 500 Internal Server Error | ||
| DATA_LOSS = 15; | ||
| } |
Oops, something went wrong.