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
The nodejs_gapic_library targets were migrated to gapic-generator-typescript
which doesn't use gapic_yaml, rendering that attribute unused. Instead it uses
the proto annotations & grpc_service_config, which this change reflects.
PiperOrigin-RevId: 314206960
1) Update to latest gapic-generator (has iam resource names fix for java).
2) Fix non-trivial issues with oslogin (resources defined in sibling package to the one they are used from) and monitoring.
3) Fix trivial missing dependencies in proto_library targets for other apis.
This is to prepare the repository to being populated with BUILD.bazel files for all supported apis (101 API) in all 7 languages.
PiperOrigin-RevId: 281618750
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
Google APIs