List Regions
const url = 'https://example.com/topology/v1/engines/example/regions';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/topology/v1/engines/example/regionsReturns a paginated list of regions for a provider. Regions are read-only inventory built by the provider sync source.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The cloud provider to list, or - for all providers
Query Parameters
Section titled “Query Parameters ”The maximum number of regions to return. The service may return fewer than this value. If unspecified, at most 20 regions will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token from a previous ListRegions call.
An AIP-160 filter expression.
An AIP-132 ordering expression.
Responses
Section titled “ Responses ”OK
ListRegionsResponse
Response message for ListRegions.
object
The list of regions
Region
A region in the Qibdo Cloud topology — the backing-cluster analog that groups zones. Regions are read-only inventory built by the per-provider sync source; they are never user-created and move only through the location lifecycle verbs. Every field is server-managed.
object
The unique identifier of the region
The DNS-label handle of the region (e.g. “us-east-1”), immutable
A human-readable label for the region (e.g. “US East (N. Virginia)”)
The usability status of the region
The cloud provider that backs the region
The multi-region this region belongs to, if any (at most one)
The timestamp when the region was created
The timestamp when the region was last updated
Qibdo-specific region detail.
object
The backing Kubernetes cluster handle (a region corresponds to a cluster). May be empty.
A token to retrieve the next page, or empty if there are no further pages.
Example
{ "regions": [ { "status": "LOCATION_STATUS_UNSPECIFIED", "engine": "ENGINE_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}