build: replicate tonic tls features
Changes
ring is not maintained anymore and could lead to compilation issues. We need a way to use the tonic exporter with https without relying on ring. This PR replicates the way tonic handles TLS by separating the ring feature from the others.
This PR also introduces a tls-aws-lc feature so that users can rely on it.
Merge requirement checklist
- [x] CONTRIBUTING guidelines followed
- [ ] Unit tests added/updated (if applicable)
- [ ] Appropriate
CHANGELOG.mdfiles updated for non-trivial, user-facing changes - [ ] Changes in public API reviewed (if applicable)
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: jdrouet / name: Jérémie Drouet (23f5864e83b946246997949cecc29eb73b8ac80b, 2834bd59d23486aec5d18a51a360e138a8e60c93, 621864f9e391157cfc388633c145ada182ddb623)
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 80.5%. Comparing base (07bb613) to head (621864f).
Additional details and impacted files
@@ Coverage Diff @@
## main #3180 +/- ##
=====================================
Coverage 80.5% 80.5%
=====================================
Files 129 129
Lines 23286 23286
=====================================
Hits 18748 18748
Misses 4538 4538
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.