-
Notifications
You must be signed in to change notification settings - Fork 197
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
Improve configurability of connectors #984
Conversation
41a6a47
to
c9c67c8
Compare
A new doc preview is ready to view. |
A new doc preview is ready to view. |
A new generated diff is ready to view.
|
A new generated diff is ready to view.
|
A new generated diff is ready to view.
|
A new doc preview is ready to view. |
529a1a2
to
465c3fa
Compare
A new generated diff is ready to view.
|
A new doc preview is ready to view. |
A new doc preview is ready to view. |
A new generated diff is ready to view.
|
A new doc preview is ready to view. |
A new generated diff is ready to view.
|
A new doc preview is ready to view. |
A new generated diff is ready to view. |
Motivation and Context
Description
Currently it's possible to use a fully custom connector with generated clients, but it's more cumbersome when using
aws-config
. Furthermore, the type ofTcpConnector
wasn't ideal since it didn't actually work when HTTPS was needed.This change:
tcp_connector
to accept anything that Hyper can useprovider_config
method (perhaps this should be namedconfigure
for symmetry?) toConfigLoader
Testing
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesCHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.