Add missing fields as per S3 specification

[balamurugana]

• listBuckets(ListBucketsArgs) breaks backward compatibility due to
  unlimited bucket listing

[shtripat]

lgtm

[shtripat]

do we plan to implement this in future with details?

[balamurugana]

I do not see any fields in S3 specification. It is empty ATM

[tabiStein]

Hi @balamurugana , apologies if this is the wrong avenue for such a question; I didn't find contact instructions in the project readme.

I'm wondering, do you know when the changes from this PR will make it to the next release? I'm currently using the latest release (8.5.17), where CompleteMultipartUploadOutput is still missing the "ChecksumCRC64NVME" field and (if I'm reading correctly) needs to be renamed to CompleteMultipartUploadResult. I believe this is resulting in the warning below in our logs every time there's an upload to S3.

I think this is not really causing problems, because I can see from the Minio client code that the warning is logged despite successful upload, but I'd like to keep track of when we can upgrade and stop seeing this in our logs.

"message": "S3 service returned unknown XML for CompleteMultipartUpload REST API. <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\n<CompleteMultipartUploadResult xmlns=\"http://s3.amazonaws.com/doc/2006-03-01/\"><Location>REDACTED</Location><Bucket>REDACTED</Bucket><Key>REDACTED</Key><ETag>REDACTED</ETag><ChecksumCRC64NVME>REDACTED</ChecksumCRC64NVME><ChecksumType>FULL_OBJECT</ChecksumType></CompleteMultipartUploadResult>",
"logger_name": "io.minio.S3Base"

Thanks for your time!