GLOBUS COLLECTION DELETE
DESCRIPTION
Delete an existing Collection.
This requires that you are an owner or administrator on the Collection.
Endpoint owners and administrators may delete Collections on the Endpoint. For Guest Collections, administrators of the Mapped Collection may also delete.
If the collection has the 'delete_protection' property set to true, the Collection can not be deleted.
All Collection-specific roles and 'sharing_policies' are also deleted.
If a Mapped Collection is deleted, then all Guest Collections and roles associated with it are also deleted.
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"
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.