[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.

Tag: Branch: Tree: ba9086de65

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ba9086de65'

${ noResults }

data-plane-api/envoy/config/bootstrap

History

data-plane-api(CircleCI) fcd3ca7b7f admin/xDS: prepare for full /config_dump and version support (#3199) ... This change does several things: 1) Clarifies how we handle xDS version_info in responses and sets us up for both top-level/transactional versions as well as per-resource versions in the future. 2) Moves the config_dump admin endpoint to the v2alpha namespace so that we can iterate on it in the future. 3) Fills out the config dump proto for the remaining resource types. These are not implemented but are here to force a discussion about how we want to handle versions moving forward. 4) Fixes RDS static config dump to actually work and add better tests. 5) Wire up version for the RDS config dump on a per-resource basis. Once we agree on the general version semantics I will be following up with dump capability of the remaining resource types. Part of https://github.com/envoyproxy/envoy/issues/2421 Part of https://github.com/envoyproxy/envoy/issues/2172 Fixes https://github.com/envoyproxy/envoy/issues/3141 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ ada758739907628b50079b9adfccf5481ec9fc5f		7 years ago
..
v2	admin/xDS: prepare for full /config_dump and version support (#3199)	7 years ago