[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: 2d9ad683cb

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '2d9ad683cb'

${ noResults }

data-plane-api/test/build

History

data-plane-api(CircleCI) 5d91278309 api/build: switch to only package level targets in API. (#8495) ... As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7		5 years ago
..
BUILD	api/build: switch to only package level targets in API. (#8495)	5 years ago
build_test.cc	api/build: migrate UDPA proto tree to external cncf/udpa repository. (#8017)	5 years ago
go_build_test.go	api: add go proto generation script (#8155)	5 years ago