JustinKyleJames

I am doing multipart upload with libs3.

I am also getting the same error when trying this. In my case the source and destination were in the same bucket.

I believe the fix should be to not add this if we are doing an UploadPartCopy but only if we are doing a CopyObject. See: https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html vs https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html https://github.com/bji/libs3/blob/287e4bee6fd430ffb52604049de80a27a77ff6b4/src/request.c#L392-L412 I...

> I like the flexibility of note 3 above... perhaps consider `SERVER_LIST=server1.irods.org:/lustre_mount/resource1` (using a colon instead of a comma... like we do for `iadmin mkresc`. Would also need to consider...

> Alternate name could be `HOST_LIST`... discush... That sounds good to me.

We have decided that allowing the user to set the vault path in the host_list string is not advisable at this time so we've removed this functionality. The reason is...

> The registrations issue is very subtle... do we just disallow non-vault registrations into unixfilesystem resources configured as detached? That seems... a brittle solution. > Or... do we allow it...

> Other than clang-format and clang-tidy, is this PR complete? Has it been tested? Yes, it is complete and has been tested. I ran clang-format and didn't see anything changed...

This has previously been reported in irods/irods#6880.

> one conflict now This was the one I referred to earlier. The previous change must have been merged in the meantime. Will resolve.