You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We still have the open issue of how to specify TLS is enabled in the case where tls_settings are not needed (ie you just want default TLS config). This is a followup to #933.
Do you do:
endpoint: https://localhost:1234
endpoint: unix+tls:///var/run/sock
I think we (@bogdandrutu and @ccaraman) started discussing it but couldn't come to a conclusion.
The text was updated successfully, but these errors were encountered:
jrcamp
changed the title
TLS client config unification
How to indicate TLS is enabled with default settings for clients
Jan 28, 2021
jrcamp
changed the title
How to indicate TLS is enabled with default settings for clients
How to indicate TLS is enabled with default settings for HTTPS clients
Jan 28, 2021
typeHTTPClientSettingsstruct {
// The target URL to send data to (e.g.: http://some.url:9411/v1/traces).Endpointstring`mapstructure:"endpoint"`// TLSSetting struct exposes TLS client configuration.TLSSetting configtls.TLSClientSetting`mapstructure:",squash"`
}
I think this is solved for HTTP clients (https has to be included as part of the endpoint). May need to figure out something else for unix sockets later but can deal with it when the need arises. @bogdandrutu do you remember these discussions? Anything else to add for this ticket?
We still have the open issue of how to specify TLS is enabled in the case where tls_settings are not needed (ie you just want default TLS config). This is a followup to #933.
Do you do:
I think we (@bogdandrutu and @ccaraman) started discussing it but couldn't come to a conclusion.
The text was updated successfully, but these errors were encountered: