Skip to content

fix(java-managed-identities): fix copy rules to allow generated v1beta1#12829

Draft
zhumin8 wants to merge 1 commit intomainfrom
fix-missing-managed-identities-v1beta1
Draft

fix(java-managed-identities): fix copy rules to allow generated v1beta1#12829
zhumin8 wants to merge 1 commit intomainfrom
fix-missing-managed-identities-v1beta1

Conversation

@zhumin8
Copy link
Copy Markdown
Contributor

@zhumin8 zhumin8 commented Apr 17, 2026

Fix deep-copy-regex in java-managed-identities/.OwlBot-hermetic.yaml to allow generated code for v1beta1 to be copied to output destination.

v1beta1 of java-managed-identities was added to the generation_config.yaml as part of initial migration to hermetic build: 14b7346, but client library code for v1beta1 is not present in java-managed-identities/google-cloud-managed-identities dir. This is due to deep-copy-regex being too strict and does not copy /v1beta1 from staging dir to final output.

Expect generation workflow to add code for v1beta1.

For #12736
For googleapis/librarian#5370

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the regex patterns in the .OwlBot-hermetic.yaml file for the java-managed-identities library. The source path regex for proto, grpc, and gapic components was modified to use (v.*) instead of (v\d), allowing the bot to correctly identify and copy versioned directories that contain more than a single digit (e.g., v1beta1). I have no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant