Chiebot-Mirror
/
data-plane-api
mirror of https://github.com/envoyproxy/data-plane-api.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
[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.
1177 Commits
2 Branches
0 Tags
17 MiB
Tag: Branch: Tree: e8d789bd7a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e8d789bd7a'
${ noResults }
data-plane-api/test/build/BUILD

34 lines
1.0 KiB
Raw Normal View History Unescape

fix bazel query (#5886) fix bazel query Risk Level: Low Testing: built //source/exe:envoy-static Signed-off-by: Dan Rosen <mergeconflict@google.com> Mirrored from https://github.com/envoyproxy/envoy @ d841d20b101584786d4d44190a78da313768b146
6 years ago
load("@envoy_api//bazel:api_build_system.bzl", "api_cc_test", "api_go_test")
bazel: various fixes to assist the Google import. (#99)
8 years ago
licenses(["notice"]) # Apache 2
api_cc_test(
test/api: basic C++ build/link test, minor RLDS fix. (#90) This is useful in Travis CI (and also internally at Google in our CI) to validate basic build/link of the protos. This exposed a small issue with API compatibility. Since we don't have additional package namespaces for each individual API, there was a conflict between the RateLimit mesage in RLDS and RDS. The quick fix was to move the RLDS message inside the response object (this is fine as nobody is using the v2 RLDS yet, open to alternatives including per-xDS API namespaces).
8 years ago
name = "build_test",
srcs = ["build_test.cc"],
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
deps = [
"//envoy/api/v2:pkg_cc_proto",
"//envoy/service/accesslog/v2:pkg_cc_proto",
"//envoy/service/discovery/v2:pkg_cc_proto",
"//envoy/service/metrics/v2:pkg_cc_proto",
"//envoy/service/ratelimit/v2:pkg_cc_proto",
config: breadcrumb annotations to infer earlier API message versions. (#9166) This PR avoids having to include an API type database in the Envoy build by introducing a message annotation option that allows Envoy to determine earlier corresponding message types via descriptor inspection. The ApiTypeDb is now ApiTypeOracle and utilizes these annotations. Risk level: Low Testing: Existing API and verison upgrade tests pass. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 297f7a73b3f93bccf8af73c0a555ae52bce6cecb
5 years ago
"@com_github_cncf_udpa//udpa/service/orca/v1:pkg_cc_proto",
test/api: basic C++ build/link test, minor RLDS fix. (#90) This is useful in Travis CI (and also internally at Google in our CI) to validate basic build/link of the protos. This exposed a small issue with API compatibility. Since we don't have additional package namespaces for each individual API, there was a conflict between the RateLimit mesage in RLDS and RDS. The quick fix was to move the RLDS message inside the response object (this is fine as nobody is using the v2 RLDS yet, open to alternatives including per-xDS API namespaces).
8 years ago
],
)
Create bazel rules for Go gRPC client libraries (#340) Add Go bazel rules for protos and gRPC. Signed-off-by: misterwilliam <misterwilliam@google.com>
7 years ago
Refactor go BUILD targets. (#406) Created new definitions in api_build_system.bzl that wrap go_proto_library, go_grpc_library, and go_test. Changed rules in api/BUILD and test/build/BUILD to use these new definitions. In the future these definitions could be expanded upon for auto generation in api_proto_library. Signed-off-by: Kyle Myerson <kmyerson@google.com>
7 years ago
api_go_test(
Create bazel rules for Go gRPC client libraries (#340) Add Go bazel rules for protos and gRPC. Signed-off-by: misterwilliam <misterwilliam@google.com>
7 years ago
name = "go_build_test",
size = "small",
srcs = ["go_build_test.go"],
importpath = "go_build_test",
deps = [
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
"//envoy/api/v2:pkg_go_proto",
"//envoy/api/v2/auth:pkg_go_proto",
api: organize go_proto_libraries (#8003) Fixes #7982 Defines a package level proto library and its associated internal go_proto_library. Deletes all existing api_go_proto_library, api_go_grpc_library, and go_package annotations in protos (they are not required and pollute the sources). I deliberately avoided touching anything under udpa since it's being moved to another repository. Risk Level: low Testing: build completes Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ d504fde0ffd97017d1ddff8caa9a3b46bba9ae48
5 years ago
"//envoy/config/bootstrap/v2:pkg_go_proto",
"//envoy/service/accesslog/v2:pkg_go_proto",
"//envoy/service/discovery/v2:pkg_go_proto",
"//envoy/service/metrics/v2:pkg_go_proto",
"//envoy/service/ratelimit/v2:pkg_go_proto",
"//envoy/service/trace/v2:pkg_go_proto",
Create bazel rules for Go gRPC client libraries (#340) Add Go bazel rules for protos and gRPC. Signed-off-by: misterwilliam <misterwilliam@google.com>
7 years ago
],
)