Review MinIO's test suite (mint) to find potential improvements to requirements for Object Versioning

[ferristocrat]

Motivation/Why?

Our integration test suites are quite good at finding edge cases in certain features of S3. We should review them to find any potential edge cases that PRD doesn't list as requirements.

What needs to be done?

Review object versioning tests from MinIO's test suite (mint) to find any potential edge cases. Verify them against the Requirements section of this document.

Acceptance Criteria

Additional edge cases are reported in the document as suggestions or comments, and product managers are aware of changes that need to be made to the requirements documents.

Paul proposes to review JT's change to implement versioning in our MinIO fork (see https://github.com/storj/gateway-mt/issues/351#issuecomment-1679485153).

Links

• https://github.com/storj/roadmap/issues/23
• https://github.com/storj/mint
• https://github.com/minio/mint

[ferristocrat]

Make sure to cover the following S3 endpoints:

• PutBucketVersioning: Sets the versioning state of an existing bucket.
• GetBucketVersioning: Returns the versioning state of a bucket.
• ListObjectVersions: Returns metadata about all versions of the objects in a bucket.
• GetObject: Retrieves objects from Amazon S3. You can specify a version ID to retrieve a specific version of the object.
• PutObject: Adds an object to a bucket. If versioning is enabled, a new version of the object is created.
• DeleteObject: Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object. If versioning is not enabled, it permanently deletes the object.

[amwolff]

JT says that MinIO's mint test suite is very basic and doesn't test the whole breadth of the versioning feature of the S3 protocol.

JT's change to implement versioning in our MinIO fork: https://review.dev.storj.io/c/storj/gateway/+/10925

Paul proposes to review JT's change as part of this task.