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

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'e8d789bd7a'

${ noResults }

data-plane-api/envoy/data

History

data-plane-api(CircleCI) c7d8aeb5c2 api: link to previous message type package in API BUILD files. (#9210) ... * api: link to previous message type package in API BUILD files. We need to include the descriptors from the previous message version in the build. We opt to do this transitively; when you include v3 of a package, you get the v2 via a transitive dep. This should work based on alwayslink semantics for cc_library. The computation of the deps is based on the previous_message_type annotation, which will allow cross package migrations. Part of #8082. Risk level: Low Testing: Disabled ip_tagging v2 descriptor hack, observed version_integration_test. After the BUILD changes, this now passes again. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 7f8fb9509d3189819dd253e25ec76e939ae106e7		5 years ago
..
accesslog	api: link to previous message type package in API BUILD files. (#9210)	5 years ago
cluster/v2alpha	protoxform: normal next free field annotation (#8433)	5 years ago
core	api: link to previous message type package in API BUILD files. (#9210)	5 years ago
tap	api: link to previous message type package in API BUILD files. (#9210)	5 years ago