-
Notifications
You must be signed in to change notification settings - Fork 23
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
wip: refreshable *tls.Config support for CGR clients #725
base: develop
Are you sure you want to change the base?
Conversation
Generate changelog in
|
|
||
"github.com/palantir/pkg/refreshable" | ||
"github.com/palantir/pkg/tlsconfig" | ||
werror "github.com/palantir/witchcraft-go-error" | ||
"github.com/palantir/witchcraft-go-logging/wlog/svclog/svc1log" | ||
) | ||
|
||
type RefreshableTLSConf interface { |
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.
nit: Spell out RefreshableTLSConfig
to match tls.Config
_, ok := r.Current().(*tls.Config) | ||
if !ok { | ||
// TODO(smenon): proper error msg. | ||
return errors.New("invalid type for refreshable") |
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.
generally we are ok with panicking if the type of a refreshable is incorrect (as it's programmer error and should easily get caught the first time the code runs) so I don't think you need NewValidatingRefreshable here
Before this PR
After this PR
==COMMIT_MSG==
==COMMIT_MSG==
Possible downsides?