[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.
 
 
 
 
 
data-plane-api(CircleCI) 38249244f7 http: global connection manager per-stream idle timeouts. (#3879) 7 years ago
.circleci ci: remove docs/format jobs. (#619) 7 years ago
bazel grpc-json: handle google.api.HttpBody when building HTTP response (#3793) 7 years ago
ci ci: remove docs/format jobs. (#619) 7 years ago
diagrams Incremental XDS proposal. (#3470) 7 years ago
docs health check: structured active healthcheck logging (#3176) 7 years ago
envoy http: global connection manager per-stream idle timeouts. (#3879) 7 years ago
examples/service_envoy
test Fixes #3756 by creating a new api_proto_library_internal build rule that (#3764) 7 years ago
tools access log service: cleanup and docs (#3494) 7 years ago
.clang-format
.gitignore
API_OVERVIEW.md Reconcile envoyproxy/data-plane-api and envoyproxy/envoy (#3036) 7 years ago
BUILD Reconcile envoyproxy/data-plane-api and envoyproxy/envoy (#3036) 7 years ago
CONTRIBUTING.md api: trivial change to test data-plane-api mirroring. (#3086) 7 years ago
LICENSE
README.md api: some fixups post repo merge. (#3103) 7 years ago
STYLE.md style: add note about alpha protos (#576) 7 years ago
WORKSPACE Fix bazel fetch command by providing //external:python_headers (#471) 7 years ago
XDS_PROTOCOL.md Incremental XDS proposal. (#3470) 7 years ago

README.md

Data plane API

This tree hosts the configuration and APIs that drive Envoy. The APIs are also in some cases used by other proxy solutions that aim to interoperate with management systems and configuration generators that are built against this standard. Thus, we consider these a set of universal data plane APIs. See this blog post for more information on the universal data plane concept.

Repository structure

The API tree can be found at two locations:

Further API reading