-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add v1beta2
of secretmanager
#10577
Conversation
@JoeWang1127 I see that the config yaml does not have google-cloud-java/generation_config.yaml Lines 1531 to 1539 in 80495ad
but there is a proto folder in the library: Was this library recently removed? |
|
Gotcha, thanks for checking. I'll follow up with removing v1beta1 from the monorepo. |
Is this(removal of a GAPIC version) something our scripts can handle automatically in the future? |
It should probably be handled by @JoeWang1127 's upcoming scripts, for now, can you manually run the generation script and add the changes as part of this PR? |
@blakeli0 the google-cloud-java/java-secretmanager/.OwlBot.yaml Lines 22 to 27 in 0416bfb
Do we want to remove this preserve regex? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should probably be handled by @JoeWang1127 's upcoming scripts, for now, can you manually run the generation script and add the changes as part of this PR?
@blakeli0 the generation went well after a small tweak to the owlbot yaml. This is something we need to add to the release notes.
Edit: added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is another point in favor of normalizing the owlbot yaml regexes
SGTM. |
@blakeli0 Looks like the deep-remove regexes only delete part of the proto and grpc libraries. google-cloud-java/java-secretmanager/.OwlBot.yaml Lines 18 to 19 in d61155f
I will add a commit to manually remove the v1beta1 libraries. This confirms that it's not enough with simply removing an api version from |
No description provided.