
jdave
Thank you Tom.. i appreciate the full response.. in my case i want to keep Wasabi immutable and not delete anything even if the user tries, i would love to see that S3Drive recognize that the 'delete' was not successful and continue to show that the file exists, as right now the file is missing from S3drive but does exist in Wasabi. I have flushed the cache and rebuilt the search data, but the files still does not show up in S3drive.
Right, so we checked how it works. Wasabi S3 bucket behaves differently depending if versioning is enabled.
If versioning is enabled, then regardless of Compliance / Object Lock settings, it is possible to delete an object. Deleting an object created so called: "Delete marker". It is possible to preview all historical versions and restore to any of them, however it is not possible to delete any version from the system until Retention Time has passed.
If versioning is disabled, then deleting an object is not possible, because without versioning enabled it would have to delete the object permanently.
In a next release which we shall be able to deploy early next week there will be options to Delete/Restore versions and to preview deleted file versions in Trash. There will be also improvements in terms of error handling, e.g. deleting a version restricted by Compliance Settings is not possible, so it shall render clear 403 / Access Denied error.
If things go well, we shall be able to also build a generic: "Versions" view which would show technically all recently changed files in the bucket and would allow to delete specific revision(s).
There is also an issue with error reporting in S3Drive when versioning is disabled and Compliance Settings enabled. During delete, file seemingly gets deleted, and disappears from the screen, but when screen gets refreshed the entry persist, this is because currently we're using quiet delete, which ignores delete error from Wasabi. We'll have it fixed.
Please find couple screenshots which shows the error reporting (it doesn't exactly work like that in a current S3Drive version, but'll be fixed next week) when trying to delete a version restricted by Compliance Settings. I've created a file, then overwritten it with version 2, then deleted it and then uploaded version 3 (so I can have it displayed again and click on the "Show versions" feature). I've then tried to delete one of the revisions which failed as expected.