mirror of
https://github.com/windmill-labs/windmill.git
synced 2026-08-18 16:02:10 +00:00
36f574ff95
* feat(cli): add object-storage commands and flow test-step * docs(cli): clarify flow test-step doesn't recurse into aiagent tools * fix(cli): correct failure step id in docs, handle bare flow.yaml path
1.7 KiB
1.7 KiB
Object Storage CLI
wmill object-storage (alias wmill s3) exposes the workspace's object storage (S3-compatible: AWS S3, MinIO, GCS, R2, Azure Blob) over the per-workspace /job_helpers/* endpoints.
Key concepts (not obvious from per-command --help)
file_keyis the path inside the bucket (e.g.reports/2026-05/orders.csv), not a Windmill path. Do NOT passu/...orf/...here — those are Windmill paths to scripts/flows/resources, unrelated to objects in the bucket.- Scope is the active workspace. Object storage is configured per-workspace (default storage + optional secondary storages). Switching workspaces switches which bucket the commands target.
--storage <name>targets a secondary storage configured on the workspace. Omit it to use the workspace's default object storage. Usewmill object-storage listto discover configured storages.previewvsdownload:previewreturns a peek (CSV first rows, text content, or a byte slice via--bytes-from/--bytes-length) without writing to disk. Usedownloadwhen you want the full file on disk.
Choosing a subcommand
- Look at what's there:
wmill object-storage files [prefix](aliasls) — paginated, use--markerto continue. - Inspect one file:
wmill object-storage info <file_key>for size/mime/last-modified,wmill object-storage preview <file_key>for content peek. - Move data in:
wmill object-storage upload <local_path> <file_key>— set--content-typeif the receiver cares (e.g.text/csv). - Move data out:
wmill object-storage download <file_key> [output_path]—--stdoutto pipe. - Reorganize:
wmill object-storage move <src> <dest>(same storage),wmill object-storage delete <file_key>(interactive confirm unless--yes).