Delete Objects Reply of Azure Using S3 Is Different than AWS

[shirady]

Environment info

• NooBaa Version: current master (5.14)
• Platform: minikube 1.30.1

Actual behavior

1. When using the s3 command of delete objects to delete objects that don't exist we get an error 'The specified blob does not exist'.

Expected behavior

1. When using the s3 command of delete objects to delete objects that don't exist we get in the reply the DeleteObject of the keys that were not exist. In AWS we can delete objects that don't exist - see here:

Note that if the object specified in the request is not found, Amazon S3 returns the result as deleted.

Although Azure returns an error, we use S3 and we expect it to behave the same as AWS.

Steps to reproduce

1. I found it out while I was trying to add unit tests to file test_s3_ops.js during the work on #7329.
2. You can copy the unit tests from the mentioned PR and remove the part of put object (before using delete objects).

More information - Screenshots / Logs / Other output

Here is a screenshot of a test I was trying to add, you can read the error message:

[github-actions[bot]]

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.

[github-actions[bot]]

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.

[github-actions[bot]]

This issue is stale and had no activity for too long - it will now be closed.