patch: Add option to disable ssl.VERIFY_X509_STRICT #350
+53
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since Python 3.13, ssl.VERIFY_X509_STRICT is enabled by default. Old Kubernetes clusters might have certificates that do not (yet) comply with that. Add a (custom) configuration option to disable this flag.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #350 +/- ##
=======================================
Coverage 27.05% 27.06%
=======================================
Files 805 805
Lines 98706 98717 +11
=======================================
+ Hits 26704 26715 +11
Misses 72002 72002 ☔ View full report in Codecov by Sentry. |
tomplus
approved these changes
Feb 11, 2025
|
Thanks for you contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since Python 3.13, ssl.VERIFY_X509_STRICT is enabled by default.
Old Kubernetes clusters might have certificates that do not (yet) comply with that.
Add a (custom) configuration option to disable this flag.
Fix #349