Skip to content

Conversation

@twilligon
Copy link

A few services expect service=s3 when this is not currently inferred by aws4fetch, such that they don't work "by default":

This detects their hostnames (*.digitaloceanspaces.com and *.linodeobjects.com) and follows the existing pattern for R2 and B2 detection to set the service parameter. Also added test coverage for both providers with virtual-host and path-style URLs. I think this is all correct, LMK if it needs edits!

A few services expect the `service` parameter to be set to `s3` where
this is not currently inferred, such that "default" aws4fetch use fails
with authentication errors. We already handle this case for R2 and B2,
but we were missing Linode Object Storage and DigitalOcean Spaces:

mhart#15
twilligon/git-lfs-s3-proxy#10

Handle `service` as we do for R2 and B2 so aws4fetch works by default.
Also, add virtual-host and path-style URL tests for both providers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant