Use TLS lib v4 to manage certs #385
Draft
+1,758
−2,410
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Reduce the code that must be managed by the o11y team.
Solution
Use the latest version of the TLS Interface Library (V4)
Context
The new version of the library attempts to encapsulate the boilerplate code needed to manage TLS certificates. This should largely (or entirely) replace cert_handler in most projects.
I'm making this PR to show how easy it should be to upgrade. I hope that using this as a template, you will be able to retire
cert_handler
entirely from every project. If not, please provide feedback on what could be improved!Testing Instructions
Since I am largely unfamiliar with the project, I have relied on the e2e tests.
Upgrade Notes