Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow string CA path values for gitlab.verify_ssl #1015

Conversation

ahills
Copy link

@ahills ahills commented Oct 11, 2023

In bugwarrior.services.gitlab.GitlabClient._fetch(), the verify_ssl configuration value is given as the requests verify parameter, which can either be a boolean or a path to a CA certificate bundle:

https://docs.python-requests.org/en/latest/user/advanced/#ssl-cert-verification

Simply extending the configuration type to include bugwarrior.config.ExpandedPath allows users to use non-public certificate authorities without disabling TLS verification entirely. This is preferable to setting the REQUESTS_CA_BUNDLE environment variable, which may interfere with other services using different certificate authorities.

Andrew Hills and others added 2 commits October 11, 2023 12:49
In bugwarrior.services.gitlab.GitlabClient._fetch(), the verify_ssl
configuration value is given as the requests verify parameter, which can
either be a boolean or a path to a CA certificate bundle:

https://docs.python-requests.org/en/latest/user/advanced/#ssl-cert-verification

Simply extending the configuration type to include bugwarrior.config.ExpandedPath
allows users to use non-public certificate authorities without disabling
TLS verification entirely. This is preferable to setting the REQUESTS_CA_BUNDLE
environment variable, which may interfere with other services using
different certificate authorities.
This fixes the docs build which was failing in CI.
@ryneeverett ryneeverett merged commit eb19a70 into GothenburgBitFactory:develop Nov 4, 2023
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants