Skip to main content
A Volume has no versions: its current contents are its contents. The walkthrough is mounting a governed folder.

Worked examples

Then reference it from a job:

Notes the flag table cannot carry

  • tp volume push uploads everything under the directory, minus OS and Office noise. Raise --concurrency on a fast link; the right number depends on the link.
  • A volume reference never carries @version. A version suffix is refused when the spec is parsed.
  • tp volume rm without --path deletes the volume itself, not just its files.
  • Downloading a volume’s files is off until its owner turns it on, and there is no CLI command that fetches them.

Check it worked

tp volume ls lists the volume with its file count. Inside a running job the files are at $VOLUMES_DIR/<leaf name>, read-only.

tp volume

Volumes a job can mount

tp volume create

Create an empty volume

tp volume imports

Copies into a volume, and how they are going
No options beyond --help.

tp volume ls

List the volumes you can reference
No options beyond --help.

tp volume push

Add files to a volume, from here or from storage the platform can reach

tp volume rm

Delete a volume, or files inside it