An update to Go gRPC Protobuf generation will change service registration function signatures to use an interface instead of a concrete type in generated .pb.go service files. This change should affect very few client library users. See release notes advisories in https://github.com/googleapis/google-cloud-go/pull/11025.
PiperOrigin-RevId: 817164257
chore: disallow "transport=rest" for services where numeric enums are not confirmed to be supported (except in PHP and Java)
PiperOrigin-RevId: 493113566
In particular this applies to Java and Python microgenerators.
With this change `java_gapic_*` and `py_gapic_*` rules mean microgenerator versions. The monolith versions of the rules are named as `java_gapic_*_legacy` and `py_gapic_*_legacy` respectively.
Also change Ads BAZEL template to reflect the change in default rule names.
Also change `DO NOT OVERRIDE` comment warnings meaning (to reflect that now by default microgenerator rules are generated and the generated version must be accepted only if the API is being migrated to the microgenerator).
PiperOrigin-RevId: 346227314
This makes googleapis forward compatible with Bazel incompatible change https://github.com/bazelbuild/bazel/issues/8922.
This CL was created by adding @rules_proto to the WORKSPACE file and then running:
find . -name BUILD.bazel | \
while read build; do \
buildifier --lint=fix --warnings=load $build; \
done
Since buildifier cannot be told not to reformat the BUILD file, some files are reformatted.
PiperOrigin-RevId: 280356106
