source-cooperative / source-cooperative/data.source.coop
source.coop endpoint is not compatible with the minio client
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24
- Forks
- 6
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 1
Description
Description of Bug:
Note: I think this counts as a bug rather than a feature request because minio client should work out-of-the-box with an endpoint that implements the S3v4 API (or even partially implements it, like CEPH).
Steps to Reproduce:
see official docs
Expected Behavior:
We should be able to initialize the minio client to perform operations against the source.coop API, like any other S3 endpoint.
Actual Behavior:
mc alias set sc https://data.source.coop
Enter Access Key: XXX
Enter Secret Key: XXX
mc: <ERROR> Unable to initialize new alias from the provided credentials. Query deserialize error: missing field `list-type`.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the documented mc alias set sc https://data.source.coop command and inspect how the source.coop endpoint handles the S3 API request involving the missing list-type field. Done means the MinIO client can initialize an alias and perform operations against the source.coop API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100