-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[configtls] Use configtls.NewDefaultClientConfig instead of manually creating struct #11383
Labels
Comments
mackjmr
changed the title
[configtls] Use confighttp.NewDefaultClientConfig instead of manually creating struct
[configtls] Use configtls.NewDefaultClientConfig instead of manually creating struct
Oct 7, 2024
Hello @mackjmr ! Is this open for contribution? |
Hi @wasim-nihal, yes this is open for contributions! I've listed in the issue descriptions the components in which this needs to be changed, please link the PRs when you open them similarely to what is done in open-telemetry/opentelemetry-collector-contrib#35457 🙂 |
wasim-nihal
added a commit
to nokia/open-telemetry-opentelemetry-collector
that referenced
this issue
Nov 11, 2024
…instead of manually creating struct. See: open-telemetry#11383 Signed-off-by: wasim-nihal <[email protected]>
wasim-nihal
added a commit
to nokia/open-telemetry-opentelemetry-collector
that referenced
this issue
Nov 18, 2024
… NewDefaultConfig() and NewDefaultServerConfig() instead of manually creating struct. See: open-telemetry#11383 Signed-off-by: wasim-nihal <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you're reporting
Move away from manually creating configtls.ClientConfig in favor of using configtls.NewDefaultClientConfig.
This is necessary for the following components:
The text was updated successfully, but these errors were encountered: