fovus job sync¶
fovus job sync¶
Sync job files from a running job to Fovus Storage.
Only running jobs can be synced.
fovus job sync [OPTIONS]
Options
- --job-id <job_id>¶
The ID of the job to sync files from.
- --job-directory <job_directory>¶
The directory of the job to sync files from. The job directory must be initialized by the Fovus CLI.
- --include-paths <include_paths>¶
The relative paths to files or folders inside the JOB_DIRECTORY that will be synced. Paths are provided with support for Unix shell-style wildcards.
You can only provide either –include-paths or –exclude-paths, not both.
Supported wildcards: * - matches any number of characters ? - matches any single character
E.g. taskName/out?/*.txt matches any .txt file in folders taskName/out1, taskName/out2, etc.
E.g. taskName???/folder/file.txt matches taskName001/folder/file.txt, taskName123/folder/file.txt, etc.
To specify multiple paths, this option may be provided multiple times or deliminated by a comma (
,
). To escape a comma, use two commas (,,
).E.g. –include-paths “path1” –include-paths “path2”
E.g. –include-paths “path1,path2”
- --exclude-paths <exclude_paths>¶
The relative paths to files or folders inside the JOB_DIRECTORY that will not be synced. Paths are provided with support for Unix shell-style wildcards.
You can only provide either –include-paths or –exclude-paths, not both.
Supported wildcards: * - matches any number of characters ? - matches any single character
E.g. taskName/out?/*.txt matches any .txt file in folders taskName/out1, taskName/out2, etc.
E.g. taskName???/folder/file.txt matches taskName001/folder/file.txt, taskName123/folder/file.txt, etc.
To specify multiple paths, this option may be provided multiple times or deliminated by a comma (
,
). To escape a comma, use two commas (,,
).E.g. –exclude-paths “path1” –exclude-paths “path2”
E.g. –exclude-paths “path1,path2”