Get Storage Class Instance
const url = 'https://example.com/storage/v1/engines/qibdo/storage-classes/example/instances/example';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/qibdo/storage-classes/example/instances/exampleReturns a single instance by unique ID under its parent storage class (or -).
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The parent storage class id, or - to look up regardless of class (AIP-159).
The unique identifier of the instance to retrieve.
Responses
Section titled “ Responses ”OK
The per-region materialization of a global storage class tier — the reconciler-managed record of whether that tier is actually provisioned in one region’s backing store. A tier is declared once, globally; an instance answers “is the tier ready in region R, and where”. qibdo-only: AWS, GCP, and Azure storage classes are globally available with no per-region instance.
object
The unique identifier of this instance (UUID)
The storage class tier this instance materializes (UUID)
The region this instance materializes the tier into — weak reference to a topology Location of kind REGION (UUID).
Current provisioning status of this instance.
The backing data pool placement reference, empty until the instance is AVAILABLE.
Timestamp when this instance was created (server-managed).
Timestamp when this instance was last updated (server-managed).
Example
{ "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" } ]}