Update Bucket
const url = 'https://example.com/storage/v1/workspaces/example/engines/example/buckets/example';const options = { method: 'PATCH', headers: {'Content-Type': 'application/json'}, body: '{"name":"example","display_name":"example","description":"example","location":{"id":"example","name":"example"},"default_storage_class":{"id":"example","name":"example"},"qibdo":{},"versioning":"BUCKET_VERSIONING_UNSPECIFIED"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://example.com/storage/v1/workspaces/example/engines/example/buckets/example \ --header 'Content-Type: application/json' \ --data '{ "name": "example", "display_name": "example", "description": "example", "location": { "id": "example", "name": "example" }, "default_storage_class": { "id": "example", "name": "example" }, "qibdo": {}, "versioning": "BUCKET_VERSIONING_UNSPECIFIED" }'Updates bucket properties (description, versioning, storage class).
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace the bucket belongs to
The cloud provider: qibdo, aws, gcp, or azure, or ’-’ to target across all providers
The unique identifier of the bucket to update
Query Parameters
Section titled “Query Parameters ”The set of fields to update. If omitted, all mutable fields are overwritten. See AIP-134 for field mask semantics.
Request Body required
Section titled “Request Body required ”A bucket is a workspace-scoped container that holds a set of stored objects.
Buckets can be provisioned across different cloud providers; the provider a bucket
lives on is reported by the read-only engine field.
object
The unique identifier of the bucket
The workspace this bucket belongs to
The bucket name (3–63 characters). It uses lowercase letters, digits, and hyphens within dot-separated labels, and must not be an IPv4 address.
A human-readable label for the bucket, e.g. “Production build artifacts”. Free text in any script. Never used to address the bucket. Optional; defaults to the handle (name) when omitted.
An optional human-readable description of the bucket
The region where the bucket’s data resides.
object
The referenced resource’s server-assigned identifier.
The referenced resource’s handle: the name a person reads and types.
The default storage tier for objects written to this bucket. Leave the reference empty and the bucket inherits the provider’s default tier.
object
The referenced resource’s server-assigned identifier.
The referenced resource’s handle: the name a person reads and types.
The cloud provider this bucket is provisioned on.
Timestamp when the bucket was created
Timestamp when the bucket was last updated
Attributes specific to a Qibdo-managed bucket.
object
Total size of the objects stored in this bucket, in bytes. Reported by the
storage backend and refreshed periodically, not on every read. Zero until
first measured; see reconcile_state.
Number of objects stored in this bucket. Zero until first measured; see
reconcile_state.
Cost attributed to this bucket. Zero where the bucket incurs no metered charge.
object
Cost accrued from the start of the current billing month until now.
object
The exact amount in major units, as a decimal string, for example 12.34, 100 or -0.05.
Up to 19 digits before the decimal point and up to 8 after it. Trailing zeros are removed, so
12.3400 is sent as 12.34. Some amounts are stored with fewer decimals than 8 and are
rounded when they are saved, so a value read back may be shorter than the one sent in.
The ISO-4217 currency code in uppercase, for example USD.
Forecast cost for the whole billing month. Left unset when there is no forecast yet, so that “we do not know” is never reported as a cost of zero.
object
The exact amount in major units, as a decimal string, for example 12.34, 100 or -0.05.
Up to 19 digits before the decimal point and up to 8 after it. Trailing zeros are removed, so
12.3400 is sent as 12.34. Some amounts are stored with fewer decimals than 8 and are
rounded when they are saved, so a value read back may be shorter than the one sent in.
The ISO-4217 currency code in uppercase, for example USD.
Whether the usage and cost figures reported on this bucket have been measured, and whether the most recent measurement succeeded.
Timestamp of the most recent successful measurement of the usage and cost figures. Absent until the bucket has been measured at least once.
Whether this bucket keeps earlier copies of an overwritten object, in the three states every provider distinguishes. Shared across providers, so it lives at the top level.
SUSPENDED is not “off”: it stops new versions being created while keeping every version already written, and those keep costing storage. Collapsing it into a boolean is what makes a bill inexplicable.
Responses
Section titled “ Responses ”OK
Storage Operation
An acknowledgment of a mutation request, carrying tracking metadata, errors, and warnings. Follows GCP’s Operations pattern (AIP-151).
object
Operation ID
Unique identifier for this operation.
Resource ID
The ID of the resource affected by this operation. May be empty for async operations where the resource does not yet exist.
Resource Type
The type of resource (e.g., “com.qibdo.cloud.storage:bucket”).
Operation Type
The kind of mutation that was requested.
Status
Current lifecycle state of the operation.
Insert Time
When the operation was first created.
Start Time
When the operation started executing.
End Time
When the operation completed (either successfully or with errors).
Errors
Business rule errors encountered during the operation.
Operation Error
A structured error returned inside an operation when a business rule fails.
object
Error Code
Numeric identifier following the S_SSS_EEE convention.
Description
Human-readable explanation of the error.
Reason
Machine-readable error identifier in UPPER_SNAKE form — the same dispatch
key google.rpc.ErrorInfo.reason carries on the synchronous error plane.
Warnings
Non-fatal notices about the operation.
Operation Warning
A non-fatal notice attached to an operation.
object
Warning Code
Numeric identifier following the S_SSS_EEE convention.
Description
Human-readable explanation of the warning.
Progress
Percentage of completion (0-100).
Scope Type
The category of scope the operation ran in or was triggered from. STORAGE_SCOPE_TYPE_UNSPECIFIED when the operation is not scoped.
Scope ID
The resource this operation was scoped to — for example, when scope_type is STORAGE_SCOPE_TYPE_WORKSPACE this is the workspace id. Empty for STORAGE_SCOPE_TYPE_PLATFORM, which has no scoped resource, and when unscoped.
Principal ID
Who performed or triggered the operation, whether a person or a machine account. Always populated: platform-driven work records the reserved system principal, so every audit record names an actor.
Trace ID
W3C trace id, for correlating this operation with the traces and log lines of the request that caused it. Empty when the operation ran with no trace context — a scheduled or event-driven action rather than a request.
Example
{ "operation_type": "STORAGE_OPERATION_TYPE_UNSPECIFIED", "status": "STORAGE_OPERATION_STATUS_UNSPECIFIED", "scope_type": "STORAGE_SCOPE_TYPE_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" } ]}