-
Notifications
You must be signed in to change notification settings - Fork 867
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
object_store: add support for using proxy_url for connection testing #3109
Conversation
1843c0d
to
25558d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you. Just some minor nits.
Do you have any recommendations on how to test this out?
2ca5ac1
to
35e9482
Compare
added some unit-test. tried it against a local socks5 server |
35e9482
to
cbfd34c
Compare
@@ -561,6 +571,14 @@ impl AmazonS3Builder { | |||
let bucket = self.bucket_name.context(MissingBucketNameSnafu)?; | |||
let region = self.region.context(MissingRegionSnafu)?; | |||
|
|||
let clientbuilder = match self.proxy_url { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This currently only alters the client used to obtain credentials, it does not alter the client created in S3Client::new
which likely needs the same treatment as AzureClient
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, thanks for the review :-)
Is this PR ready to go? |
cbfd34c
to
a1c7906
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is good to go, I just want to test it working locally and then I think it can go
Benchmark runs are scheduled for baseline = 1d6b5ab and contender = b2bfe9c. b2bfe9c is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #2989
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?