Possibility to truly (physically) delete files

[Daniel-WWU-IT]

When using the usual CS3API calls to delete a file, that file is not physically deleted but moved into a recycle bin. This is extremely problematic when performing health checks: These checks upload about 100kb per run and delete the files afterwards. However, since these files are only moved to some other place, they quickly pile up, resulting in full volumes.

As uploading files is an essential check, we either need (a) an option to truly delete files, (b) a way of clearing the recycle bin of the current user (might already be there), (c) another workaround.

[Daniel-WWU-IT]

I worked around this issue by purging the user's recycle bin after execution. But this might still be worth some consideration...

[labkode]

I think this is related purely to the implementation of the localfs backend, perhaps an option should be added to this driver to skip trashbin by means of a configuration line?

[Daniel-WWU-IT]

Would certainly make sense, since deleted files can really pile up quickly. For the health checks, this additional cleanup works fine, but files from other users would pile up in the same way, so...