chore: librarian generate pull request: 20260225T153341Z#15609
Merged
Conversation
Contributor
Summary of ChangesHello @parthea, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the Compute Engine v1beta client library by integrating recent API revisions. The primary focus is on expanding functionality through the addition of new services for managing instant snapshot groups and reservation slots. It also incorporates new resource parameters and types across existing services, enhancing the library's coverage of the Compute Engine API. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request, generated by the Librarian CLI, updates the Cloud Client Libraries from protos. The changes are extensive, introducing new services like InstantSnapshotGroups, RegionInstantSnapshotGroups, and ReservationSlots, along with their corresponding clients, documentation, and metadata. My review identified several docstring formatting issues that affect readability, and these comments have been retained as they do not contradict any provided rules. The rest of the auto-generated changes appear to be correct and consistent.
Comment on lines
+1721
to
+1738
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1809
to
+1823
| Note: Use the following APIs to manage network endpoint | ||
| groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such as zonal NEGs, | ||
| hybrid connectivity NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope (such as regional | ||
| internet NEGs, serverless NEGs, Private Service | ||
| Connect NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope (such as global | ||
| internet NEGs):global API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - | |
| To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - | |
| To manage NEGs with global scope (such as global | |
| internet NEGs):global API | |
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1945
to
+1959
| Note: Use the following APIs to manage network endpoint | ||
| groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such as zonal NEGs, | ||
| hybrid connectivity NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope (such as regional | ||
| internet NEGs, serverless NEGs, Private Service | ||
| Connect NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope (such as global | ||
| internet NEGs):global API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - | |
| To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - | |
| To manage NEGs with global scope (such as global | |
| internet NEGs):global API | |
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1178
to
+1195
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal API | |
| - To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - To manage NEGs with global scope | |
| (such as global internet NEGs): global | |
| API | |
Comment on lines
+1926
to
+1943
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1438
to
+1455
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal API | |
| - To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - To manage NEGs with global scope | |
| (such as global internet NEGs): global | |
| API | |
Comment on lines
+1816
to
+1833
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1908
to
+1922
| Note: Use the following APIs to manage network endpoint | ||
| groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such as zonal NEGs, | ||
| hybrid connectivity NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope (such as regional | ||
| internet NEGs, serverless NEGs, Private Service | ||
| Connect NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope (such as global | ||
| internet NEGs):global API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - | |
| To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - | |
| To manage NEGs with global scope (such as global | |
| internet NEGs):global API | |
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+2061
to
+2075
| Note: Use the following APIs to manage network endpoint | ||
| groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such as zonal NEGs, | ||
| hybrid connectivity NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope (such as regional | ||
| internet NEGs, serverless NEGs, Private Service | ||
| Connect NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope (such as global | ||
| internet NEGs):global API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - | |
| To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - | |
| To manage NEGs with global scope (such as global | |
| internet NEGs):global API | |
| Note: Use the following APIs to manage network endpoint | |
| groups: | |
| - To manage NEGs with zonal scope (such as zonal NEGs, | |
| hybrid connectivity NEGs): zonal API | |
| - To manage NEGs with regional scope (such as regional | |
| internet NEGs, serverless NEGs, Private Service | |
| Connect NEGs): regional API | |
| - To manage NEGs with global scope (such as global | |
| internet NEGs): global API | |
Comment on lines
+1178
to
+1195
| Note: Use the following APIs to manage | ||
| network endpoint groups: | ||
|
|
||
| - | ||
| To manage NEGs with zonal scope (such | ||
| as zonal NEGs, hybrid connectivity | ||
| NEGs): zonal | ||
| API | ||
| - | ||
| To manage NEGs with regional scope | ||
| (such as regional internet NEGs, | ||
| serverless NEGs, Private Service Connect | ||
| NEGs): regional API | ||
| - | ||
| To manage NEGs with global scope | ||
| (such as global internet NEGs):global | ||
| API | ||
|
|
Contributor
There was a problem hiding this comment.
The formatting of this note in the docstring has some issues with indentation and extra spaces, which affects readability and the rendered documentation. It would be better to format it as a clean list.
Suggested change
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - | |
| To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal | |
| API | |
| - | |
| To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - | |
| To manage NEGs with global scope | |
| (such as global internet NEGs):global | |
| API | |
| Note: Use the following APIs to manage | |
| network endpoint groups: | |
| - To manage NEGs with zonal scope (such | |
| as zonal NEGs, hybrid connectivity | |
| NEGs): zonal API | |
| - To manage NEGs with regional scope | |
| (such as regional internet NEGs, | |
| serverless NEGs, Private Service Connect | |
| NEGs): regional API | |
| - To manage NEGs with global scope | |
| (such as global internet NEGs): global | |
| API | |
daniel-sanche
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR created by the Librarian CLI to generate Cloud Client Libraries code from protos.
BEGIN_COMMIT
BEGIN_NESTED_COMMIT
feat: Update Compute Engine v1beta API to revision 20260206
(googleapis/googleapis#1159)
PiperOrigin-RevId:
Library-IDs: google-cloud-compute-v1beta
Source-link: googleapis/googleapis@dc505966
END_NESTED_COMMIT
BEGIN_NESTED_COMMIT
feat: Update Compute Engine v1beta API to revision 20260106 (#1147)
PiperOrigin-RevId:
Library-IDs: google-cloud-compute-v1beta
Source-link: googleapis/googleapis@d4b17263
END_NESTED_COMMIT
END_COMMIT
This pull request is generated with proto changes between
googleapis/googleapis@cfe62b3c
(exclusive) and
googleapis/googleapis@dc505966
(inclusive).
Librarian Version: v0.7.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:160860d189ff1c2f7515638478823712fa5b243e27ccc33a2728669fa1e2ed0c