Syntax and options for `uip or buckets`, which manages Orchestrator storage containers used by automations.

Manage Orchestrator buckets — storage containers for files used by automations. Bucket operations are folder-scoped. For per-file operations inside a bucket, see uip or bucket-files.

For the cross-resource conventions (auth, folder scoping, key types, output envelope), see the uip or overview.

List buckets. Requires --folder-path, --folder-key, or --all-folders. With a folder, lists buckets inside that folder. With --all-folders, lists across every accessible folder (optionally excluding one via --exclude-folder-path / --exclude-folder-key, which apply only in that mode). Filter: -n, --name <name>. --sort-by <field> sorts results (default Id desc); --all-fields returns the full API response.

Get bucket details by key. --all-fields returns the full API response, including storage container, credential-store link, and tags.

Create a bucket in a folder. Requires <name>. Optional flags include --identifier <guid> (auto-generated if omitted), -d, --description, --storage-provider <Azure|Amazon|Minio|S3Compatible|FileSystem> (omit for Orchestrator built-in), --storage-parameters, --storage-container, --credential-store-key (required for Azure and Amazon), --external-name, --password, --options <None|ReadOnly|AuditReadAccess|AccessDataThroughOrchestrator>, --tags <json> (a JSON array, e.g. '[{"name":"env","value":"prod"}]').

Update bucket properties by key. Same flags as create (all optional; -n, --name renames the bucket on update).

Delete a bucket by key. Requires -y, --yes — the CLI never prompts for destructive operations. Refuses to delete a bucket that still has files unless you also pass -f, --force (which deletes the files too, and implies --yes).

Add or remove the bucket from a folder.

List the folders a bucket is shared with.

See Exit codes for the shared contract. delete exits 1 if -y, --yes / -f, --force is omitted, or if the bucket still has files and --force was not passed.