Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion librarian.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,6 @@ libraries:
- path: google/cloud/alloydb/v1beta
- path: google/cloud/alloydb/v1alpha
copyright_year: "2026"
skip_generate: true
- name: google-cloud-apigateway
version: 4.2.2
apis:
Expand Down
19 changes: 0 additions & 19 deletions packages/google-cloud-alloydb/.OwlBot.yaml

This file was deleted.

31 changes: 15 additions & 16 deletions packages/google-cloud-alloydb/.repo-metadata.json
Original file line number Diff line number Diff line change
@@ -1,17 +1,16 @@
{
"name": "alloydb",
"name_pretty": "AlloyDB API",
"product_documentation": "https://cloud.google.com/alloydb/docs",
"client_documentation": "https://cloud.google.com/nodejs/docs/reference/alloydb/latest",
"issue_tracker": "https://github.com/googleapis/google-cloud-node/issues",
"release_level": "stable",
"language": "nodejs",
"repo": "googleapis/google-cloud-node",
"distribution_name": "@google-cloud/alloydb",
"api_id": "alloydb.googleapis.com",
"default_version": "v1",
"requires_billing": true,
"library_type": "GAPIC_AUTO",
"api_shortname": "alloydb"
}

"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_id": "alloydb.googleapis.com",
"api_shortname": "alloydb",
"client_documentation": "https://cloud.google.com/nodejs/docs/reference/alloydb/latest",
"default_version": "v1",
"distribution_name": "@google-cloud/alloydb",
"issue_tracker": "https://issuetracker.google.com/issues/new?component=1194526&template=1689942",

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.

This URL is correct, but it doesn't appear to grant users permission to create issues. We should escalate this to the AlloyDB team. @pearigee what's the best path forward here?

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.

I am not sure. We will need to check Teams or the Buganizer queue to see who owns it and ping them directly.

"language": "nodejs",
"library_type": "GAPIC_AUTO",
"name": "alloydb",
"name_pretty": "AlloyDB",
"product_documentation": "https://cloud.google.com/alloydb/docs",
"release_level": "stable",
"repo": "googleapis/google-cloud-node"
}
Loading