List S3 buckets in a project.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/objectstorage/buckets \ --header 'Authorization: Bearer <token>'The project’s buckets with their reconciler-driven
status (creating/available/deleting/error). Cedar-gated on s3:ListBuckets.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Buckets.
object
A tenant S3 bucket + its reconciler-driven status.
object
Reconciler-driven lifecycle phase. delete_blocked is terminal: a non-empty bucket whose delete returned BucketNotEmpty — empty it and re-issue the delete, or force-purge.
When the bucket entered its current status (bumped only on an actual status-value change, unlike a churning updatedAt) — lets an operator tell a just-created creating from a long-stuck one.
object
Client-facing S3 endpoint host for this bucket’s region — the value for aws --endpoint-url. Omitted when no public endpoint is configured (a dev install with no front-door domain).
Path-style bucket URL (<scheme>://<endpoint>/<bucket>). Omitted when no endpoint.
Virtual-host-style bucket URL (<scheme>://<bucket>.<endpoint>). Present only for a DNS-name endpoint (the front-door s3.
True when the server had more rows than it returned. The response is a valid prefix of the result, not the whole of it.
Without this flag a client at the server’s row ceiling receives a full
page and no nextPageToken, which means “this is
the complete set” — so data it never saw would be indistinguishable
from data that does not exist.
It does not imply a cursor exists. These queries do not all sort on a total order, so a resumable token cannot be minted for them yet. The remedy is to narrow the request (a filter, or a tighter scope), not to page.
Example
{ "items": [ { "status": "creating" } ]}Authenticated but not authorized.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}