Joe Wang
Joe Wang
The unit tests in `hermetic_build/release_note_generation/tests/generate_pr_description_unit_tests.py` have real `git clone` and `git checkout`. However, it is not a best practice for unit tests to depend on internet request as it is...
Currently, the integration test (`hermetic_build/library_generation/tests/integration_tests.py`) uses a branch (`chore/test-hermetic-build`) in [google-cloud-java](https://github.com/googleapis/google-cloud-java) to verify the generation result. This setting makes it not obvious on how to change the golden files. We...
Current, most of the library parameters, e.g., `api_shortname`, `api_description`, etc., comes from the generation configuration. Some parameters can be read from service yaml and we can remove them from the...
The `release_level` of each library is hardcoded in the generation configuration. We should set the value according to the library version such that it should be `stable` if the library...
In this PR: - Rename Logging section to Advanced Logging Setup. A preparation step to introduce Client Library Debug Logging.
Graalvm nightly build failed with ``` ╷ │ Error: Provider produced inconsistent result after apply │ │ When applying changes to │ module.java_iam_admin.google_service_account.service_account, provider │ "provider[\"[registry.terraform.io/hashicorp/google\](https://www.google.com/url?q=http://registry.terraform.io/hashicorp/google%5C&sa=D)"]" produced an │ unexpected...
The CI status in README.md is broken, for example: https://github.com/googleapis/google-cloud-java/blob/main/java-accessapproval/README.md#ci-status