Now, if you configure your cloud storage to prevent any deletion by Orthanc for security reasons, Orthanc will complain about not being able to delete files (which is obviously neither a bug, nor “something strange”, but your own configuration decision).
Oh, you’re right, but it’s a more mixed-up issue.
Since a few month Google Cloud Storage set the default Soft delete policy to true.
So, I think Orthanc (I didn’t checked the source code) enforce a real deletion, not a soft delete. That’s why we saw the log and our error. By setting OverwriteInstances to true we indeed bypass the issue.
Maybe the fix is to allow a soft delete on the object storage (at least on GCS)?
Source : https://cloud.google.com/resources/storage/soft-delete-announce
