-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Remove squash on configtls.TLSClientSetting
in contrib
#5433
Comments
@Aneurysm9 , please assign me this issue! |
This was referenced Sep 24, 2021
tigrannajaryan
pushed a commit
that referenced
this issue
Oct 4, 2021
6 tasks
povilasv
referenced
this issue
in coralogix/opentelemetry-collector-contrib
Dec 19, 2022
* Implement unmarshal metrics with jsoniter * Implement unmarshal metrics with jsoniter AND add test file * add unit testing * add unit testing * git rebase main * do a matrix testing for all 8 cases for a combination of these 3 bool options. * some func is deprecated * go imports * go imports * Update change log * generate the 8 cases per tested func to avoid repeating test case definition * 1. Remove instrumentationLibraryMetrics and instrumentation_library_metrics. 2. Some functions move to pdata/internal/json 3.Ignore unknown fields and have a debug log for them * add test unit * update CHANGELOG * remove the new API AND reuse the other API NewJSONUnmarshaler * update CHANGELOG * update CHANGELOG * go mod tidy * remove unnecessary return true on the default branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
Based on this PR (open-telemetry/opentelemetry-collector#4063) in collector repo, configtls.TLSClientSetting should be defined as
mapstructure: "tls,omitempty"
.Below links are files where changes are needed:
The text was updated successfully, but these errors were encountered: