GLOBUS RENAME

NAME

globus rename - Rename a file or directory on an endpoint.

globus rename [OPTIONS] ENDPOINT_ID SOURCE_PATH DEST_PATH

Rename a file or directory on an endpoint.

The old path must be an existing file or directory. The new path must not yet
exist.

The new path does not have to be in the same directory as the old path, but
most endpoints will require it to stay on the same filesystem.

--local-user TEXT: Optional value passed to identity mapping specifying which local user account to map to. Only usable with Globus Connect Server v5 mapped collections.
-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"

Rename a directory:

$ ep_id=aa752cea-8222-5bc8-acd9-555b090c0ccb
$ globus rename $ep_id:~/tempdir $ep_id:~/project-foo

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.