Recursive Deletes

Gateway utilizes Swarm's recursive deleting mechanism with some augmentation for requests not containing a "recursive={value}" query argument.

See https://perifery.atlassian.net/wiki/spaces/public/pages/2443811307 and https://perifery.atlassian.net/wiki/spaces/public/pages/2443821292 for more about recursive deletes of domains and buckets.

Gateway automatically adds "recursive=yes" to the DELETE request transmitted to Swarm when removing an empty storage domain or an empty bucket if the client request does not include the recursive query argument. This preserves the protocol behavior of the Gateway versions before 4.0. This is analogous to the Unix rmdir behavior on empty directories.

The request must include the recursive query argument or else the request fails if a client issues a DELETE on a non-empty storage domain or bucket. This is analogous to attempting to run rmdir on a non-empty directory in Unix.

The Gateway client audit log records the single DELETE operation. The individual objects do not receive individual audit log records of deletion even if the delete is permitted and the domain or bucket contains objects.

Delay

Some deletes may be subject to a delay period although Swarm's recursive deletes are always asynchronous. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443821292 for explanation of the "recursive=yes" and "recursive=now" delete options.

Important

Content UI uses the "recursive=now" delete option for storage domain and bucket removal.