Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow transparent usage of s3 interfaces using s3v2 signature_version #86

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

tktridley
Copy link

Added a config variable "signature_version" that is set through trying an s3v4 signature first, then falls back to s3v2 through excepting on a ClientError if s3v4 isn't accepted by the s3 interface.

This is required for transparently allowing users to connect to S3 interfaces that cannot be updated to use the s3v4 signature_version.

Tom Ridley and others added 4 commits July 22, 2022 16:57
Fixed function definition
Added try/except behaviour to support S3 interfaces with old signature_version
@tktridley
Copy link
Author

Hi, apologies for the issues with DCO. I'm not sure how to solve this issue. Would closing this pull request, rebasing my branch with --signoff, and opening a new pull request (directly from the branch on my fork) be preferable, or is there someway to correct this within this pull request?

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