Skip to content

Conversation

@amanda-tarafa
Copy link
Contributor

Changes in this PR will be published to Nuget on the next release cycle.

@amanda-tarafa amanda-tarafa requested a review from a team as a code owner November 19, 2025 22:27
@gemini-code-assist
Copy link

Summary of Changes

Hello @amanda-tarafa, 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 various Google Cloud API definitions, primarily through an automated regeneration process. The changes encompass a wide range of services, introducing new functionalities, refining existing descriptions, and ensuring consistency across the API surface. Key updates include expanded regional support for database services, enhanced integration features for API management, and more granular reporting metrics for advertising platforms. This regeneration aims to keep the client libraries aligned with the evolving capabilities of the underlying Google Cloud services.

Highlights

  • API Regeneration: This pull request introduces a comprehensive API regeneration across multiple Google Cloud services, updating their API definitions to reflect the latest features and improvements.
  • New Features in AlloyDB: AlloyDB APIs (v1, v1alpha, v1beta) now include extensive regional endpoint definitions, new view parameters for backup operations (including BACKUP_VIEW_CLUSTER_DELETED), and new fields for maintenanceVersionSelectionPolicy, maintenanceVersionName, and isDeletionProtectionEnabled in various resource schemas.
  • API Hub Addons and Gateway Configurations: The API Hub API (v1) has been significantly expanded with new addons resources, including methods for get, list, and manageConfig. It also introduces new schemas for Addon, AddonConfig, AllDataAddonConfig, ApigeeEdgeConfig, ApigeeOPDKConfig, ApigeeXHybridConfig, EnvironmentFilter, GatewayPluginAddonConfig, GatewayPluginConfig, ListAddonsResponse, ManageAddonConfigRequest, and SourceEnvironment, enhancing its extensibility and integration capabilities.
  • Microsoft Entra ID Integration in Cloud SQL: Cloud SQL Admin APIs (v1, v1beta4) now support Microsoft Entra ID (formerly Azure Active Directory) integration, with new methods like ListEntraIdCertificates and RotateEntraIdCertificate for managing Entra ID certificates. New schemas such as InstancesListEntraIdCertificatesResponse, InstancesRotateEntraIdCertificateRequest, RotateEntraIdCertificateContext, SqlInstancesAddEntraIdCertificateRequest, and SqlServerEntraIdConfig have been added to facilitate this integration. Additionally, ENTRAID_USER has been added to the User.Type enum.
  • Enhanced Metrics and Ad Management in Search Ads 360: The Search Ads 360 API (v0) now provides more detailed metrics including averageCartSize, averageImpressionFrequencyPerUser, averageOrderValueMicros, costOfGoodsSoldMicros, grossProfitMargin, grossProfitMicros, orders, revenueMicros, uniqueUsers, and unitsSold. Ad management capabilities are improved with new fields like finalAppUrls, finalMobileUrls, finalUrlSuffix, and trackingUrlTemplate in AdGroupAd and CampaignCriterion resources. New asset field types LONG_DESCRIPTION and CALL_TO_ACTION have also been added.
  • Deprecation of Legacy Content API Resources: The Content API for Shopping (v2.1) has removed the returnaddress and returnpolicy resources and their associated schemas, indicating a shift towards newer or consolidated functionalities for managing returns.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist
Copy link

Summary of Changes

Hello @amanda-tarafa, 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 primarily focuses on an extensive API regeneration across various Google Cloud services, ensuring that the API definitions are up-to-date with the latest features and improvements. It introduces new capabilities in services like AlloyDB, Android Publisher, APIhub, Cloud Deploy, and Cloud SQL, enhancing database management, app monetization, API governance, deployment automation, and identity integration. Additionally, several API descriptions and parameter explanations have been refined for better clarity and accuracy.

Highlights

  • API Definitions Updated: Numerous API definitions across various Google Cloud services have been regenerated, incorporating the latest schema changes and API revisions.
  • New Features in AlloyDB: AlloyDB now supports new regional endpoints, introduces a 'view' parameter for backup operations, and adds fields like 'clusterDeleted', 'maintenanceVersionSelectionPolicy', and 'maintenanceVersionName' for enhanced management.
  • Enhanced Android Publisher API: The Android Publisher API includes new schemas for subscription pricing phases (BaseDetails, FreeTrialDetails, IntroductoryPriceDetails, ProrationPeriodDetails), external account identifiers, and item replacement details, offering more granular control and information for app publishers.
  • APIhub Addons and Gateway Configurations: The APIhub service now features a new 'addons' resource with methods for getting, listing, and managing addon configurations, including specific configurations for Apigee Edge, OPDK, and X/Hybrid gateways, and support for source environment details.
  • Cloud Deploy Tool Version Management: Cloud Deploy introduces explicit tool version management for releases, allowing users to specify Docker, Helm, Kpt, Kubectl, and Kustomize versions, along with conditions to track their support status.
  • Cloud SQL Entra ID Integration: Cloud SQL now supports Microsoft Entra ID integration, including new methods to list, rotate, and add Entra ID certificates, and configuration options for SQL Server instances.
  • Search Ads 360 Metrics and URL Management: Search Ads 360 gains new metrics related to shopping performance (e.g., average cart size, gross profit) and expanded URL management fields for ads and ad groups, including final app URLs and tracking URL templates.
  • General Description and Parameter Clarifications: Many API descriptions have been updated for clarity, including changes from 'G Suite' to 'Google Workspace', and clarifications for parameters like 'returnPartialSuccess' across multiple services.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@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 contains a large number of changes from an automated API regeneration process. It includes updates to many APIs, such as admin, alloydb, androidpublisher, cloudresourcemanager, merchantapi, sqladmin, and more. The changes include adding new features (like new endpoints, resources, methods, and fields), improving documentation for clarity, and updating dependencies. I've also noted several breaking changes, such as the removal of resources in the Content API and changes to method signatures in Cloud Resource Manager API, which are likely intentional but should be clearly communicated in the release notes. I've added specific comments on these breaking changes. Overall, the regeneration seems correct and consistent.

@gemini-code-assist
Copy link

Summary of Changes

Hello @amanda-tarafa, 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 represents a routine, automated regeneration of API definitions across a broad spectrum of Google Cloud services. The primary purpose is to synchronize the API surface with the latest backend changes, ensuring that developers using these APIs have access to the most current features, improved descriptions, and updated functionalities. This update is crucial for maintaining compatibility and enabling the adoption of new capabilities across the Google Cloud ecosystem.

Highlights

  • API Updates Across Multiple Services: This pull request includes regenerated API definitions for numerous Google Cloud services, reflecting the latest changes in their respective APIs. This ensures that client libraries and tools are up-to-date with the most recent features and improvements.
  • New Features for AlloyDB: AlloyDB APIs (v1, v1alpha, v1beta) now support new regional endpoints, a 'view' parameter for backup listing and retrieval, and new fields like 'maintenanceVersionSelectionPolicy', 'maintenanceVersionName', and 'isDeletionProtectionEnabled' for clusters and instances.
  • Enhanced Android Publisher API: The Android Publisher v3 API introduces several new schemas and fields related to subscription management, including 'BaseDetails', 'ExternalAccountIds', 'FreeTrialDetails', 'ItemReplacement', 'OfferPhaseDetails', 'OutOfAppPurchaseContext', and 'ProrationPeriodDetails', providing more granular control and information for in-app purchases and subscriptions.
  • API Hub Addons Management: The API Hub v1 API now includes new resources and methods for managing 'addons', allowing users to get, list, and configure addons with various settings for different gateway types like Apigee Edge, OPDK, and X/Hybrid.
  • Cloud SQL Entra ID Integration: The SQL Admin API (v1 and v1beta4) now supports listing and rotating Entra ID certificates, adding Entra ID certificates, and includes new configuration options for SQL Server Entra ID and server certificate rotation modes, enhancing security and identity management for SQL Server instances.
  • Improved Dataform and Storage Transfer Capabilities: Dataform v1 and v1beta1 APIs now support specifying connection details, file formats (like Parquet), storage URIs, and table formats (like Iceberg) for relations. Storage Transfer v1 adds 'privateNetworkService' for AWS S3 and Azure Blob Storage data sources, and a 'matchGlob' option for object conditions.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@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 contains a large number of changes across many Google Cloud APIs, consistent with an automated API regeneration process. The updates include new features, documentation improvements, and some intentional breaking changes that are part of a new API version release. The changes appear to be a correct and comprehensive update of the API client libraries, and I found no bugs or issues in the implementation.

Copy link

@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 contains a large number of automated changes from an API regeneration process. The updates span across numerous API discovery documents and their corresponding generated C# client libraries. Key changes include updating API revision numbers, adding new endpoints and features, and refining descriptions for better clarity, such as the rebranding from 'G Suite' to 'Google Workspace'. I've also noted some intentional breaking changes, like the removal of certain resources and parameters, which simplify the APIs. The generated C# code correctly reflects these updates. After a thorough review, I did not find any specific issues or bugs in the code changes. The regeneration appears to have been successful.

@amanda-tarafa
Copy link
Contributor Author

(I'll try to see what the conflicts are here)

@amanda-tarafa
Copy link
Contributor Author

Ah, no conflicts, it's just that there's a limit for Rebase and Merge of 100 commits (and we have 106). I'll pull the PR and split it in two.

@amanda-tarafa
Copy link
Contributor Author

Closing, this has been done by #3079 and #3080

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.

2 participants