[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: a83394157a

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'a83394157a'

${ noResults }

data-plane-api/envoy/admin/v2alpha

History

data-plane-api(CircleCI) a83394157a admin: expose listener name/address through /listener admin endpoint (#7131) ... The current /listeners admin endpoint only returns a JSON-encoded list of addresses/ports. If a listener config binds to port 0, the endpoint will return the port that was assigned, but if there are multiple listeners binding to port 0, there's no way to tell which listener received which port. This PR adds a proto that contains the listener's name and address. The /listeners endpoint returns this data in both text and JSON format, similar to the /clusters admin endpoint. Risk Level: Low (according to #6959 the /listeners admin endpoint is only used for testing) Testing: I updated integration_admin_test.cc to test the new output formats for the /listeners endpoint. I also updated the tools/socket_passing.py script that's used for integration/hotrestart_test. Docs Changes: new inline docs in listeners.proto updated the admin menu description of /listeners Release Notes: admin: /listener endpoint now returns :ref:listener.proto<api/envoy/admin/v2alpha/listeners.proto> Fixes #6959 Signed-off-by: Kaisen Chen <kaisen@yelp.com> Mirrored from https://github.com/envoyproxy/envoy @ 4461f431112876932e0328f6af31de7cf34fadfc		6 years ago
..
BUILD	admin: expose listener name/address through /listener admin endpoint (#7131)	6 years ago
certs.proto	…
clusters.proto	…
config_dump.proto	…
listeners.proto	admin: expose listener name/address through /listener admin endpoint (#7131)	6 years ago
memory.proto	…
metrics.proto	…
mutex_stats.proto	…
server_info.proto	…
tap.proto	…