Stop providing a hardcoded CA bundle #489
Merged
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.
The SDK no longer provides a CA bundle to verify SSL connections. This also allows us to remove the runtime dependency on
pkg_resourcesand thussetuptools.The
ca_certsparameter is still supported, so users can pin with their own CA bundle if they so choose. Otherwise, the default verification mechanism in therequestslibrary now applies (this usescertifiand/or system certificates, depending on the configuration).Improves integration tests to cover both scenarios (i.e. when a bundle is provided, and when one isn't).
Checklist
General Contributing
Is This a Code Change?
Validation
toxpass?