Summary
Having a configuration setting that forces removal of shared objects would be very useful in WiredTiger testing to clean up and could have possible uses in MongoDB if tiered storage is not shared, for example. A new, undocumented configuration string remove_shared=false|true should be implemented and tested with drop. The testing should include combinations with force and remove_files. In particular, remove_files=false,remove_shared=true should not be allowed and return an error at this time. The remove_files setting already applies to any files on local storage (including objects that are still existing locally due to local_retention). The remove_shared setting will apply to all copies of the object that the extension controls. That would include the copy of the object in the bucket and any storage cache the extension may have.