SDKs & ToolsCLI

spiral volumes

Register Volumes and manage storage credentials

Usage: spiral volumes [OPTIONS] <COMMAND>

Options

OptionRequiredDefaultDescription
--jsonnoEmit output as JSON instead of formatted tables
--json-logsnoWrite structured JSON logs to standard error

Subcommands

CommandSummary
spiral volumes lsList Volumes available to your Organization
spiral volumes registerRegister an existing bucket or prefix. Does not create a bucket or test object access
spiral volumes statusRetire, revoke, or reactivate a Volume
spiral volumes credentialReplace a Volume's credential without changing its storage root

spiral volumes ls

Usage: spiral volumes ls [OPTIONS]

Options

OptionRequiredDefaultDescription
--jsonnoEmit output as JSON instead of formatted tables
--json-logsnoWrite structured JSON logs to standard error

spiral volumes register

Usage: spiral volumes register [OPTIONS] --name <NAME> --uri <URI> --provider <PROVIDER>

Options

OptionRequiredDefaultDescription
--name <NAME>yesVolume name
--uri <URI>yesStorage root, such as s3://bucket/prefix/ or gs://bucket/prefix/
--provider <PROVIDER>yesStorage provider. AWS and GCS authenticate with OIDC, Ceph with the method --auth names, and the rest with an access key
--auth <AUTH>noHow a Ceph Volume authenticates: access_key, or oidc for the Volume's own identity
--region <REGION>noStorage region; also the signing region for AWS and S3-compatible storage
--role-arn <ROLE_ARN>noThe role the Volume assumes: an AWS IAM role that trusts the Volume's identity, or a Ceph role as the gateway prints it
--endpoint <ENDPOINT>noS3-compatible endpoint for minio, rustfs, ceph, or s3_like
--account-id <ACCOUNT_ID>noCloudflare account ID for R2
--jurisdiction <JURISDICTION>noR2 jurisdiction: eu, fedramp, or us
--workload-identity-provider <WORKLOAD_IDENTITY_PROVIDER>noGCS workload identity provider resource name
--service-account <SERVICE_ACCOUNT>noGCS service account email
--access-key-id <ACCESS_KEY_ID>noAccess key ID. Defaults to AWS_ACCESS_KEY_ID for access-key providers
--secret-file <SECRET_FILE>noRead the secret access key from a file; otherwise use AWS_SECRET_ACCESS_KEY
--jsonnoEmit output as JSON instead of formatted tables
--json-logsnoWrite structured JSON logs to standard error

spiral volumes status

Usage: spiral volumes status [OPTIONS] <VOLUME_ID> <STATUS>

Arguments

ArgumentRequiredDefaultDescription
VOLUME_IDyes
STATUSyes

Options

OptionRequiredDefaultDescription
--jsonnoEmit output as JSON instead of formatted tables
--json-logsnoWrite structured JSON logs to standard error

spiral volumes credential

Usage: spiral volumes credential [OPTIONS] --provider <PROVIDER> <VOLUME_ID>

Arguments

ArgumentRequiredDefaultDescription
VOLUME_IDyes

Options

OptionRequiredDefaultDescription
--provider <PROVIDER>yesStorage provider. AWS and GCS authenticate with OIDC, Ceph with the method --auth names, and the rest with an access key
--auth <AUTH>noHow a Ceph Volume authenticates: access_key, or oidc for the Volume's own identity
--region <REGION>noStorage region; also the signing region for AWS and S3-compatible storage
--role-arn <ROLE_ARN>noThe role the Volume assumes: an AWS IAM role that trusts the Volume's identity, or a Ceph role as the gateway prints it
--endpoint <ENDPOINT>noS3-compatible endpoint for minio, rustfs, ceph, or s3_like
--account-id <ACCOUNT_ID>noCloudflare account ID for R2
--jurisdiction <JURISDICTION>noR2 jurisdiction: eu, fedramp, or us
--workload-identity-provider <WORKLOAD_IDENTITY_PROVIDER>noGCS workload identity provider resource name
--service-account <SERVICE_ACCOUNT>noGCS service account email
--access-key-id <ACCESS_KEY_ID>noAccess key ID. Defaults to AWS_ACCESS_KEY_ID for access-key providers
--secret-file <SECRET_FILE>noRead the secret access key from a file; otherwise use AWS_SECRET_ACCESS_KEY
--jsonnoEmit output as JSON instead of formatted tables
--json-logsnoWrite structured JSON logs to standard error
Found a problem? Edit this page or report an issue.

On this page