[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: 61688e4873

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '61688e4873'

${ noResults }

data-plane-api/envoy/extensions/formatter

History

data-plane-api(Azure Pipelines) e01b00e614 access_log: metadata formatter extension (#17457) ... This PR addresses several issues: 1. MetadataFormatter base class takes a pointer to a function to access specific type of metadata. All other methods operating on internals of metadata structure are moved to base class. This simplified adding new types of metadata. 2. new type of access_log METADATA tag is introduced to handle all types of metadata. It is implemented as formatter extension. It handles existing tags DYNAMIC_METADATA and CLUSTER_METADATA, so two ways of accessing dynamic and cluster metadata are allowed now. Maybe we should obsolete DYNAMIC_METADATA and CLUSTER_METADATA in the future? 3. Adds handler for ROUTE metadata. See issue #3006. Follow up to #16121 Risk Level: Low Testing: Unit tests. Docs Changes: Yes. Release Notes: Yes. Platform Specific Features: No Signed-off-by: Christoph Pakulski <christoph@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 43b597e719230c8266998394301c5d0b3c862688		3 years ago
..
metadata/v3	access_log: metadata formatter extension (#17457)	3 years ago
req_without_query/v3	formatter: print request header without query string (#15711)	4 years ago