GitHub user Kami opened a pull request:

    https://github.com/apache/libcloud/pull/812

    Add certifi CA bundle path to Libcloud CA bundle search path if certifi is 
available

    This change will add certifi CA bundle path to Libcloud CA bundle search 
path if `certifi` library (https://pypi.python.org/pypi/certifi) is installed 
and available in the virtual environment / PYTHONPATH where Libcloud is used.
    
    This path is injected into the CA bundle search path which means it has 
precedence over other paths.
    
    This behavior is enabled by default, but it can be disabled by setting 
`LIBCLOUD_SSL_USE_CERTIFI` environment variable to `false` or any other 
non-truthy value.
    
    Some context can be found in this PR - 
https://github.com/conda-forge/staged-recipes/pull/694, but even without it, I 
think that's a good change until we switch to `requests`.
    
    ## TODO
    
    - [ ] Docs

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Kami/libcloud 
add_certifi_bundle_to_path_if_available

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/812.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #812
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to