Chiebot-Mirror
/
data-plane-api
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)
1659 Commits
2 Branches
0 Tags
18 MiB
data-plane-api/envoy/api/v2/route/route.proto

12 lines
287 B
Raw Normal View History Unescape

Draft LDS/RDS APIs and protobuf build system.
8 years ago
syntax = "proto3";
Split base API package into sub-packages (#421) Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
package envoy.api.v2.route;
api: add java proto options to avoid risk of future breakage (#5764) As discussed with @snowp in [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-456537248) and [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-457649859), adding these options will avoid the risk of having API breaking changes on the generated java code as the proto files evolve. Risk Level_: Medium Note that e.g. [envoyproxy/java-control-plane](https://github.com/envoyproxy/java-control-plane) will have to do a refactoring when they sync the proto files next time. Signed-off-by: Penn (Dapeng) Zhang <zdapeng@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4a5f85809cef13be47873483789a5a7bb64ded7c
6 years ago
[WiP] api: annotate files with package version status. (#10492) Part of https://github.com/envoyproxy/envoy/issues/10355, this patch introduces additional annotations to the API to support automatic inference (and developer documentation) of where the active developer editable version of a file is, and which files are frozen or machine generated. Risk level: Low (API annotations only) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4c5f4310bb8a19a38e5377d7a2d2dc6aa4560f47
5 years ago
import "udpa/annotations/status.proto";
api: split config from service defs for CDS/RDS/EDS/SRDS/TDS. (#9555) This allows for a clean separation of config/service in v3. This is a continuation of #9548. Risk level: Low Testing: bazel test //test/... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c3bddaee1912fcd1fedc4786aee830b2e4a7c599
5 years ago
import public "envoy/api/v2/route/route_components.proto";
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
api: options after import (#9413) In order to get file level move annotation, import has to be before options. Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 062c895f499382ae61dead16db2a7e78b9146525
5 years ago
option java_package = "io.envoyproxy.envoy.api.v2.route";
option java_outer_classname = "RouteProto";
option java_multiple_files = true;