data-plane-api/bazel/BUILD

load("@io_bazel_rules_go//proto:compiler.bzl", "go_proto_compiler")
load("//:utils.bzl", "json_data")
load(":repository_locations.bzl", "REPOSITORY_LOCATIONS_SPEC")
load(":repository_locations_utils.bzl", "load_repository_locations_spec")

licenses(["notice"])  # Apache 2

exports_files([
    "repository_locations.bzl",
    "repository_locations_utils.bzl",
])

go_proto_compiler(
    name = "pgv_plugin_go",
    options = ["lang=go"],
    plugin = "@com_envoyproxy_protoc_gen_validate//:protoc-gen-validate",
    suffix = ".pb.validate.go",
    valid_archive = False,
    visibility = ["//visibility:public"],
)

json_data(
    name = "repository_locations",
    data = load_repository_locations_spec(REPOSITORY_LOCATIONS_SPEC),
)
rename packages (#9515) Description: Move packages around for #8120 and #8121 Risk Level: Med around messing up build. Testing: CI Docs Changes: in API/STYLE.md Release Notes: N/A (v3alpha is not in use yet) Fixes #8120 Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 1371f2ef46582a72b5b3971147bd87c534011731 5 years ago			`load("@io_bazel_rules_go//proto:compiler.bzl", "go_proto_compiler")`
bazel: Add json_data and providers (#18086) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ c74b352b29e3042ab35893e83d0e9b56ba67989f 3 years ago			`load("//:utils.bzl", "json_data")`
			`load(":repository_locations.bzl", "REPOSITORY_LOCATIONS_SPEC")`
deps: Dump/interpolate repository_locations -> json (#19441) There are a few tools that require the repository_locations data, currently we are bringing that data into the python by putting the implementation (as opposed to the abstract library) in the envoy repo, this will allow us to instead pass the repo locations data as a file/cli flag, and move the implementation into the upstream tooling This PR also avoids using the old SourceFileLoader + bzl files method of loading the data, instead loading directly from the write_json rules for the repo files and interpolating There is a more generic implementation of some of what is required here in #17998 Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ f2d3f523ee4170f7ded205523526c592e2550f75 3 years ago			`load(":repository_locations_utils.bzl", "load_repository_locations_spec")`
rename packages (#9515) Description: Move packages around for #8120 and #8121 Risk Level: Med around messing up build. Testing: CI Docs Changes: in API/STYLE.md Release Notes: N/A (v3alpha is not in use yet) Fixes #8120 Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 1371f2ef46582a72b5b3971147bd87c534011731 5 years ago
build: use rules_cc and use buildifier -lint to enforce it (#11399) Commit Message: Partially address #9488. Resurrected #10597. Additional Description: Risk Level: Low Testing: CI Docs Changes: N/A Release Notes: N/A Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 67649af8d4881fb7593c728f181eff393f85a638 5 years ago			`licenses(["notice"]) # Apache 2`

docs: (take 2) Move external deps rst generation and cve scan to bazel (#15427) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ a3c9842bb97b9628bfe1076ba60eeab13b30577a 4 years ago			`exports_files([`
			`"repository_locations.bzl",`
			`"repository_locations_utils.bzl",`
			`])`

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			`go_proto_compiler(`
			`name = "pgv_plugin_go",`
			`options = ["lang=go"],`
			`plugin = "@com_envoyproxy_protoc_gen_validate//:protoc-gen-validate",`
			`suffix = ".pb.validate.go",`
			`valid_archive = False,`
			`visibility = ["//visibility:public"],`
			`)`
bazel: Add json_data and providers (#18086) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ c74b352b29e3042ab35893e83d0e9b56ba67989f 3 years ago
			`json_data(`
			`name = "repository_locations",`
deps: Dump/interpolate repository_locations -> json (#19441) There are a few tools that require the repository_locations data, currently we are bringing that data into the python by putting the implementation (as opposed to the abstract library) in the envoy repo, this will allow us to instead pass the repo locations data as a file/cli flag, and move the implementation into the upstream tooling This PR also avoids using the old SourceFileLoader + bzl files method of loading the data, instead loading directly from the write_json rules for the repo files and interpolating There is a more generic implementation of some of what is required here in #17998 Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ f2d3f523ee4170f7ded205523526c592e2550f75 3 years ago			`data = load_repository_locations_spec(REPOSITORY_LOCATIONS_SPEC),`
bazel: Add json_data and providers (#18086) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ c74b352b29e3042ab35893e83d0e9b56ba67989f 3 years ago			`)`