Add 'verify' parameter to control SSL verification behavior #362
+75
−7
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.
Description
This PR adds a new
verify
parameter to control SSL certificate verification, providing both API and CLI interfaces for this functionality. This offers a quick solution for common SSL-related issues that users have reported.Problem Solved
This change provides an immediate solution for users experiencing SSL-related issues like:
Instead of requiring users to modify environment variables or implement complex workarounds, they can now directly control SSL verification behavior through both the API and CLI.
Changes
verify
parameter toget_transcript()
,get_transcripts()
, andlist_transcripts()
methods--verify
option to CLI with support for both custom certificate paths and disabling verificationNone
to maintain backward compatibilityThe implementation follows the same pattern as Python requests'
verify
parameter, making it familiar to users who work with the requests library.Usage