-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix: NewClientFromRefreshableConfig respects SecurityConfig #701
Conversation
@@ -225,7 +223,6 @@ func newClientBuilder() *clientBuilder { | |||
KeepAlive: defaultKeepAlive, | |||
SocksProxyURL: nil, | |||
})), | |||
TLSConfig: defaultTLSConfig, |
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.
Build()
will now create a TLSConfigProvider if this is not set.
@@ -402,6 +402,12 @@ func newValidatedClientParamsFromConfig(ctx context.Context, config ClientConfig | |||
HTTP2ReadIdleTimeout: derefPtr(config.HTTP2ReadIdleTimeout, defaultHTTP2ReadIdleTimeout), | |||
ProxyFromEnvironment: derefPtr(config.ProxyFromEnvironment, true), | |||
TLSHandshakeTimeout: derefPtr(config.TLSHandshakeTimeout, defaultTLSHandshakeTimeout), | |||
TLS: refreshingclient.TLSParams{ |
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 should have been added in #689 - tests now confirm this config is plumbed through
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.
👍
Released v2.83.0 |
Fixes regression from #689, which now depends on the builder's
b.TLSConfig
being nil in case we should construct a refreshable provider.This change is