fix: correct gapic generator template logic#3185
fix: correct gapic generator template logic#3185stephaniewang526 merged 1 commit intogoogleapis:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3185 +/- ##
=========================================
Coverage 87.13% 87.13%
Complexity 6075 6075
=========================================
Files 494 494
Lines 24039 24039
Branches 2610 2610
=========================================
Hits 20946 20946
Misses 2232 2232
Partials 861 861 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Looks good to me, but please validate that it actually generates what you want for your API (and for some other api if you can find some, which relies on same type of Mocks).
To do that, please pull googleapis repo, replace the gapic-generator repository target in WORKSPACE#L62:
http_archive(
name = "com_google_api_codegen",
strip_prefix = "gapic-generator-6b03e539065bece1ce84816ec212851885bca013",
urls = ["https://github.com/stephaniewang526/gapic-generator/archive/6b03e539065bece1ce84816ec212851885bca013.zip"],
)This change makes googleapis generation to pull gapic-generator from your fork and the specific commit in it with the fix.
Then on Linux machine, go to the pulled repo root dir (googleapis) and run:
bazel test //google/cloud/bigquery/storage/v1:storage_java_gapic_test_suite
and
bazel build //google/cloud/bigquery/storage/v1:google-cloud-bigquery-storage-v1-java
The last command will put generated .tar archive (with the client in it) to the following location (relative to the build root):
bazel-bin/google/cloud/bigquery/storage/v1/google-cloud-bigquery-storage-v1-java.tar.gz
Unpack that and check that the files are what they should be.
If all that works, then LGTM
|
Hi Vadym, thanks for the instructions. I tested this change in v1alpha2 (where we introduced write api changes) and was able to verify the following in the generated tar file |
Fixes #3181