[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) 0cac03fc44 Add ability for most specific header mutations to take precedence (#8466) 5 years ago
.circleci
bazel api/build: automatically generate BUILD files. (#8506) 5 years ago
ci
diagrams
docs api/build: switch to only package level targets in API. (#8495) 5 years ago
envoy Add ability for most specific header mutations to take precedence (#8466) 5 years ago
examples/service_envoy
migration
test api/build: switch to only package level targets in API. (#8495) 5 years ago
tools api/build: switch to only package level targets in API. (#8495) 5 years ago
.clang-format
.gitignore
API_OVERVIEW.md
API_VERSIONING.md api: add API_VERSIONING.md. (#8399) 5 years ago
BUILD
CONTRIBUTING.md api: add API_VERSIONING.md. (#8399) 5 years ago
LICENSE
README.md
STYLE.md api: add API_VERSIONING.md. (#8399) 5 years ago
xds_protocol.rst docs: fix links to internal sections (#8539) 5 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