| 1 |
"""Define our protoc plugin in a rule that can be provided to go_proto_library#compilers |
| 2 |
|
| 3 |
This is in a separate BUILD file from /bazel/BUILD to avoid a dependency on rules_go for all users who load from it. |
| 4 |
|
| 5 |
If you use Gazelle, you can use a directive so that the pgv_plugin_go is automatically added to generated go_proto_library rules. |
| 6 |
See https://github.com/bazelbuild/bazel-gazelle#directives |
| 7 |
|
| 8 |
For example, in some/BUILD.bazel: |
| 9 |
# gazelle:go_grpc_compilers @com_envoyproxy_protoc_gen_validate//bazel/go:pgv_plugin_go, @io_bazel_rules_go//proto:go_grpc |
| 10 |
""" |
| 11 |
load("@io_bazel_rules_go//proto:compiler.bzl", "go_proto_compiler") |
| 12 |
|
| 13 |
go_proto_compiler( |
| 14 |
name = "pgv_plugin_go", |
| 15 |
suffix = ".pb.validate.go", |
| 16 |
valid_archive = False, |
| 17 |
plugin = "@com_envoyproxy_protoc_gen_validate//:protoc-gen-validate", |
| 18 |
options = ["lang=go"], |
| 19 |
visibility = ["//visibility:public"], |
| 20 |
) |