GLOBUS TASK GENERATE-SUBMISSION-ID
DESCRIPTION
Generate a new task submission ID for use in globus transfer and globus delete.
Submission IDs allow you to safely retry submission of a task in the presence of
network errors. No matter how many times you submit a task with a given ID, it will
only be accepted and executed once. The response status may change between
submissions.
Important Note: submission IDs are not the same as task IDs.
OPTIONS
- -v, --verbose
-
Control level of output, make it more verbose.
- --quiet
-
Suppress non-essential output. This is higher precedence than
--verbose. - -h, --help
-
Show this message and exit.
-
-F, --format
[unix|json|text] -
Output format for stdout. Defaults to text.
-
--jmespath, --jq
TEXT -
A JMESPath expression to apply to json output. Forces the format to be json processed by this expression.
-
--map-http-status
TEXT -
Map HTTP statuses to any of these exit codes: 0,1,50-99. e.g. "404=50,403=51"
EXAMPLES
Submit a transfer, using a submission ID generated by this command:
$ sub_id="$(globus task generate-submission-id)"
$ globus transfer --submission-id "$sub_id" ...EXIT STATUS
0 on success.
1 if a network or server error occurred, unless --map-http-status has been used to change exit behavior on http error codes.
2 if the command was used improperly.
3 if the command was used on the wrong type of object, e.g. a collection command used on an endpoint.
4 if the command has authentication or authorization requirements which were not met, as in ConsentRequired errors or missing logins.