Chiebot-Mirror
/
data-plane-api
mirror of https://github.com/envoyproxy/data-plane-api.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
798 Commits
2 Branches
0 Tags
17 MiB
Tag: Branch: Tree: c8457da634
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c8457da634'
${ noResults }
data-plane-api/envoy/api/v2/README.md

10 lines
468 B
Raw Normal View History Unescape

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
Protocol buffer definitions for xDS and top-level resource API messages.
Package group `//envoy/api/v2:friends` enumerates all consumers of the shared
API messages. That includes package envoy.api.v2 itself, which contains several
xDS definitions. Default visibility for all shared definitions should be set to
`//envoy/api/v2:friends`.
Additionally, packages envoy.api.v2.core and envoy.api.v2.auth are also
consumed throughout the subpackages of `//envoy/api/v2`.