Remove vendored openssl dependency#1380
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1380 +/- ##
=====================================
Coverage 81.8% 81.8%
=====================================
Files 119 119
Lines 9938 9938
=====================================
Hits 8137 8137
Misses 1801 1801 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jsuereth
left a comment
There was a problem hiding this comment.
Thanks for issuing a fix here! I'm wondering if we can more aggressive at turning off the OpenSSL requirement
| # Use vendored OpenSSL on non-Windows platforms to avoid system OpenSSL deps | ||
| # This enables the "vendored" feature for the openssl crate when building on | ||
| # non-Windows targets. | ||
| [target.'cfg(not(windows))'.dependencies] |
There was a problem hiding this comment.
Could we change this so we only vendor on MUSL deployments? I think that's the only platform where we ran into trouble and needed it...
|
We discussed in semconv tooling SIG - We're going to work on extracting the entire SSL embedding as a This is good to merge for now. |
The OTel Dataflow Engine (aka otel-arrow) has been using Weaver. In weaver due to dependency on openssl vendored feature it causes openssl build everytime. This change is made to avoid such overhead. With this change weaver will rely on windoows native tls implementation.
Part of #1382.
Part of open-telemetry/otel-arrow#2697.