Adjust DeleteBucket (forceful deletion) satellite endpoint (object retention)

[amwolff]

Goal

This issue is to make meaningful progress on Object Lock implementation within core and edge services. Specifically, to support immutable backups in backup software products like Veeam.

What needs to be done? • Acceptance Criteria

Modify the corresponding to DeleteBucket endpoint on the satellite (the endpoint might be named differently):

• Don't allow forceful deletions of the bucket with locked object versions in it

Summary

Implementation reference.

Depends on…

• 400

Links

• an easy-to-read and insightful introduction to Object Lock: Using S3 Object Lock

[kaloyan-raev]

The S3 API allows deleting only empty buckets. The forceful deletion of buckets is a Minio extension of the S3 protocol.

For the MVP, we could support forceful deletion only for buckets not configured with object lock. For those with object lock, we could just return an error that the operation is unsupported. The check should be on bucket level, and not checking individual object versions for their retention period.

[amwolff]

The check should be on bucket level, and not checking individual object versions for their retention period.

That's a good idea. I concur.

[storj-gerrit[bot]]

Change satellite/{metabase,metainfo}: make DeleteBucket respect retention mentions this issue.