Blob Archiver doesn't appear to work with s3
- Dominant language
- Go
- Stars
- 126
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
It seems like the `blob-archiver` tool has issues when running with `BLOB_ARCHIVER_DATA_STORE` set to "s3". After setting the endpoint with `BLOB_ARCHIVER_S3_ENDPOINT` pointing to my s3 URL/bucket (with the HTTPS:// prefix removed), I got
```
failed to setup: config check failed: storage config check failed: s3 config check failed: s3 bucket must be set
```
which led me to set the hidden flag `BLOB_ARCHIVER_S3_BUCKET` with my bucket name, explicitly, alongside the endpoint. Now the current error is something I'm unable to debug:
```
failed to setup: client is not active
```
I don't know what client this is referring to, but I'm assuming it's the storage client related to s3.
Right now, it does not seem like there's any way to get this set up for my team's infrastructure. Please help me debug this or suggest a workaround that can be used in the meantime.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.