Skip to content

chore: migration batch 2#16659

Open
jskeet wants to merge 50 commits intogoogleapis:mainfrom
jskeet:batch-2
Open

chore: migration batch 2#16659
jskeet wants to merge 50 commits intogoogleapis:mainfrom
jskeet:batch-2

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Apr 15, 2026

  • google-apps-card
  • google-apps-chat
  • google-apps-events-subscriptions
  • google-apps-meet
  • google-apps-script-type
  • google-area120-tables
  • google-auth
  • google-cloud-access-approval
  • google-cloud-advisorynotifications
  • google-cloud-alloydb
  • google-cloud-alloydb-connectors
  • google-cloud-api-gateway
  • google-cloud-apigee-connect
  • google-cloud-apigee-registry
  • google-cloud-apihub
  • google-cloud-api-keys
  • google-cloud-apiregistry
  • google-cloud-appengine-admin
  • google-cloud-appengine-logging
  • google-cloud-apphub
  • google-cloud-appoptimize
  • google-cloud-artifact-registry
  • google-cloud-asset
  • google-cloud-assured-workloads
  • google-cloud-audit-log
  • google-cloud-auditmanager
  • google-cloud-automl
  • google-cloud-backupdr
  • google-cloud-bare-metal-solution
  • google-cloud-batch
  • google-cloud-beyondcorp-appconnections
  • google-cloud-beyondcorp-appconnectors
  • google-cloud-beyondcorp-appgateways
  • google-cloud-beyondcorp-clientconnectorservices
  • google-cloud-beyondcorp-clientgateways
  • google-cloud-biglake
  • google-cloud-bigquery
  • google-cloud-bigquery-analyticshub
  • google-cloud-bigquery-biglake
  • google-cloud-bigquery-connection
  • google-cloud-bigquery-data-exchange
  • google-cloud-bigquery-datapolicies
  • google-cloud-bigquery-datatransfer
  • google-cloud-bigquery-logging
  • google-cloud-bigquery-migration
  • google-cloud-bigquery-reservation
  • google-cloud-bigquery-storage
  • google-cloud-billing
  • google-cloud-billing-budgets
  • google-cloud-binary-authorization

jskeet added 30 commits April 15, 2026 14:09
jskeet added 20 commits April 15, 2026 14:12
@jskeet jskeet requested a review from parthea April 15, 2026 14:15
@jskeet jskeet requested review from a team as code owners April 15, 2026 14:15
@jskeet jskeet requested review from sycai and removed request for a team April 15, 2026 14:15
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 standardizes metadata and documentation across numerous packages, primarily focusing on indentation consistency, field reordering, and the addition of missing API descriptions. Feedback highlights the need to replace non-standard HTML tags with plain text or standard reStructuredText formatting, address a placeholder description in the App Hub package, and restore an accidentally removed description in the BigQuery package.

"product_documentation": "https://cloud.google.com/alloydb/",
"release_level": "preview",
"repo": "googleapis/google-cloud-python"
"api_description": "AlloyDB for PostgreSQL is an open source-compatible database service that\nprovides a powerful option for migrating, modernizing, or building\ncommercial-grade applications. It offers full compatibility with standard\nPostgreSQL, and is more than 4x faster for transactional workloads and up\nto 100x faster for analytical queries than standard PostgreSQL in our\nperformance tests. AlloyDB for PostgreSQL offers a 99.99 percent\navailability SLA inclusive of maintenance. \u003cbr\u003e\u003cbr\u003e AlloyDB is optimized\nfor the most demanding use cases, allowing you to build new applications\nthat require high transaction throughput, large database sizes, or\nmultiple read resources; scale existing PostgreSQL workloads with no\napplication changes; and modernize legacy proprietary databases.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The api_description contains HTML <br> tags. This field should use plain text or standard newline characters (\n) for formatting to ensure compatibility with all metadata consumers.

Suggested change
"api_description": "AlloyDB for PostgreSQL is an open source-compatible database service that\nprovides a powerful option for migrating, modernizing, or building\ncommercial-grade applications. It offers full compatibility with standard\nPostgreSQL, and is more than 4x faster for transactional workloads and up\nto 100x faster for analytical queries than standard PostgreSQL in our\nperformance tests. AlloyDB for PostgreSQL offers a 99.99 percent\navailability SLA inclusive of maintenance. \u003cbr\u003e\u003cbr\u003e AlloyDB is optimized\nfor the most demanding use cases, allowing you to build new applications\nthat require high transaction throughput, large database sizes, or\nmultiple read resources; scale existing PostgreSQL workloads with no\napplication changes; and modernize legacy proprietary databases.",
"api_description": "AlloyDB for PostgreSQL is an open source-compatible database service that\nprovides a powerful option for migrating, modernizing, or building\ncommercial-grade applications. It offers full compatibility with standard\nPostgreSQL, and is more than 4x faster for transactional workloads and up\nto 100x faster for analytical queries than standard PostgreSQL in our\nperformance tests. AlloyDB for PostgreSQL offers a 99.99 percent\navailability SLA inclusive of maintenance. \n\n AlloyDB is optimized\nfor the most demanding use cases, allowing you to build new applications\nthat require high transaction throughput, large database sizes, or\nmultiple read resources; scale existing PostgreSQL workloads with no\napplication changes; and modernize legacy proprietary databases.",

PostgreSQL, and is more than 4x faster for transactional workloads and up
to 100x faster for analytical queries than standard PostgreSQL in our
performance tests. AlloyDB for PostgreSQL offers a 99.99 percent
availability SLA inclusive of maintenance. <br><br> AlloyDB is optimized
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

HTML tags like <br> are not standard reStructuredText and will likely be rendered as literal text on platforms like PyPI or GitHub. Use a blank line to separate paragraphs instead.

Suggested change
availability SLA inclusive of maintenance. <br><br> AlloyDB is optimized
availability SLA inclusive of maintenance.
AlloyDB is optimized

PostgreSQL, and is more than 4x faster for transactional workloads and up
to 100x faster for analytical queries than standard PostgreSQL in our
performance tests. AlloyDB for PostgreSQL offers a 99.99 percent
availability SLA inclusive of maintenance. <br><br> AlloyDB is optimized
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

HTML tags like <br> are not standard reStructuredText and will likely be rendered as literal text on platforms like PyPI or GitHub. Use a blank line to separate paragraphs instead.

Suggested change
availability SLA inclusive of maintenance. <br><br> AlloyDB is optimized
availability SLA inclusive of maintenance.
AlloyDB is optimized

"product_documentation": "https://cloud.google.com/app-hub/docs/overview",
"release_level": "preview",
"repo": "googleapis/google-cloud-python"
"api_description": "null ",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The api_description value "null " appears to be a placeholder or a result of an automated script error. It should be replaced with a meaningful description of the App Hub service.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jskeet PTAL

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Will merge as-is, but make a note to look later. (It's very weird to get that...)

"name": "bigquery",
"name_pretty": "Google Cloud BigQuery",
"product_documentation": "https://cloud.google.com/bigquery",
"api_id": "bigquery.googleapis.com",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The api_description field was removed in this update. This field provides essential information about the service and should be retained, consistent with other packages in this repository.

Suggested change
"api_id": "bigquery.googleapis.com",
"api_description": "is a fully managed, NoOps, low cost data analytics service.\nData can be streamed into BigQuery at millions of rows per second to enable real-time analysis.\nWith BigQuery you can easily deploy Petabyte-scale Databases.",
"api_id": "bigquery.googleapis.com",

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