List Storage Classes
const url = 'https://example.com/storage/v1/engines/example/storage-classes';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/storage/v1/engines/example/storage-classesReturns a paginated list of storage classes. A specific provider filters to that provider;
- lists storage classes across all providers.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The cloud provider: qibdo, aws, gcp, or azure, or ’-’ to list across all providers
Query Parameters
Section titled “Query Parameters ”The maximum number of storage classes to return. The service may return fewer than this value. If unspecified, at most 20 storage classes will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token, received from a previous ListStorageClasses call. Provide this to retrieve
the subsequent page. When paginating, all other parameters must match the call that provided
the page token.
AIP-160 filter expression. Filterable fields: compression_type, create_time, engine, id, is_default, name, performance_class, redundancy, update_time.
AIP-132 order_by expression. Sortable fields: compression_type, create_time, engine, name, performance_class, redundancy, update_time.
AIP-158 offset mode: number of resources to skip from the start of the filtered, sorted set. Use EITHER skip (offset paging) OR page_token (cursor paging) — never both in the same request. Supplying both is an invalid request. Default 0 (no skip).
Responses
Section titled “ Responses ”OK
ListStorageClassesResponse
Response message for ListStorageClasses.
object
The list of storage classes
object
The unique identifier of the storage class
The handle of the storage class, e.g. “standard”. Lowercase letters, digits and hyphens; letter-initial; no adjacent hyphens. Unique per engine. Used to address the tier by name or id.
A human-readable label for the storage class, e.g. “Standard”. Free text in any script. Never used to address the tier. Optional; defaults to the handle (name) when omitted.
An optional human-readable description of the storage class
Whether this is the global default tier for its provider. Buckets that omit a storage class inherit the default. At most one default exists per provider.
The cloud provider this storage class is provisioned on.
Timestamp when the storage class was created
Timestamp when the storage class was last updated
Attributes specific to a Qibdo-managed storage class.
object
The redundancy scheme the tier guarantees (replication factor or erasure-coding profile).
The performance class the tier targets (media tier).
The compression type for data in this storage class (NONE, SNAPPY, ZLIB, ZSTD, LZ4)
The per-region readiness of this tier, computed from its materialization records — one entry per region the tier has been declared in. Lets a client show where the tier is usable and, when it is not, why. Empty for providers with no per-region materialization (only Qibdo has it).
The readiness of a storage class tier in one region, summarised from its materialization record.
object
The region this entry describes. Weak reference to a topology Location of kind REGION (UUID).
The tier’s provisioning status in this region.
A short, human-readable explanation of a non-ready status (unsupported / failed / abandoned); empty when the tier is available or still pending.
A token, which can be sent as page_token to retrieve the next page. If this field is
empty, there are no subsequent pages.
Exact count of resources matching the request’s filter and scope (both pagination modes).
Example
{ "storage_classes": [ { "engine": "ENGINE_UNSPECIFIED", "qibdo": { "redundancy": "REDUNDANCY_UNSPECIFIED", "performance_class": "PERFORMANCE_CLASS_UNSPECIFIED", "compression_type": "COMPRESSION_TYPE_UNSPECIFIED" }, "availability": [ { "status": "STORAGE_CLASS_INSTANCE_STATUS_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" } ]}