If the Firestore database quota is increased beyond 100, is ListDatabases guaranteed to return all databases in a single response, and is there any undocumented service-side response-size limit?

Google Cloud Database
1

Title

Is ListDatabases supported for more than 100 Firestore databases?

Hi Team,

We are implementing Firestore monitoring using:

GET https://firestore.googleapis.com/v1/projects/{projectId}/databases

The current documented limit is 100 databases per project, but customers can request a quota increase.

Since ListDatabases does not support pageSize, pageToken, or `nextPageToken:

  1. If the quota is increased to, say, 1,000 databases, is ListDatabases guaranteed to return all 1,000 databases in a single response?

  2. Is there any service-side limit on the number of databases or response size?

  3. If not, what is the recommended API/approach for discovering more than 100 databases without making N+1 GetDatabase calls?

Thanks!

2

So I think they wont have to use pagination here (or such scenario has never arrived). It will be REST/gRPC responses which are subject to payload limits (typically 10–32 MB for Google Cloud REST APIs). GRPC request can accomodate 1000+ list of dbs in a single call. But I think there will be hardly any orgs in the world having 1000+ dbs in a single account or project.