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: 823187922
chore(python): include *.proto files in //google/api:api-py
chore(python): include *.proto files in //google/cloud:extended-operations-py
chore(python): include *.proto files in //google/cloud/location:location-py
chore(python): include *.proto files in //google/logging/type:logging-type-py
chore(python): include *.proto files in //google/longrunning:operations-py
chore(python): include *.proto files in //google/rpc:rpc-py
chore(python): include *.proto files in //google/rpc/context:rpc-context-py
chore(python): include *.proto files in //google/type:type-py
PiperOrigin-RevId: 733643032
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
