delete_file_locations support

[bwalsh]

https://ohsucomputationalbio.slack.com/archives/C043HPV0VMY/p1700260682334969

Liam Beckman
2:38 PM
Hi all, we’re plugging along on the aced-idp.org data portal and are running into an issue when attempting to delete indexd records using the Gen3 SDK. I’ve included additional info below on that, but let us know if we can add anything else or try to reproduce the issue, thank you!
 
Issue:
When attempting to delete an indexd record using the delete_file_locations() method in the Gen3 SDK, we encounter a “The AWS Access Key Id you provided does not exist” error. The indexd record is in non-AWS S3 bucket (MinIO endpoint), which is specified by the endpoint_url of the bucket in the Fence config.
 
Expected Behavior:
The delete_file_locations() method should delete both the file and the indexd record for both AWS and non-AWS S3-compatible buckets. (edited)

[bwalsh]

See #26

[lbeckman314]

Testing file removal on Local and Development deployments using the following:

• Fence PR: Feat/s3 delete files uc-cdis/fence#1127
• gen3_util files rm: f831d49

[bwalsh]

@lbeckman314 if all OK, can you close this issue? thanks

[lbeckman314]

Closed as complete, see the following PR for status on upstream merging:

uc-cdis/fence#1127 (comment)