Fix handling of self-signed certs in s3_conn#1141
Open
chess-knight wants to merge 1 commit intomainfrom
Open
Conversation
Take insecure/verify/cacert parameter from clouds.yaml and pass it to boto3.resource. If insecure is True or verify is False use verify=False also for boto3. Else, if you provide cacert(via cacert or verify parameter) it is also used for boto3. If nothing from above is met, use verify=None to keep default boto3 behaviour. Signed-off-by: Roman Hros <roman.hros@dnation.cloud>
This file contains hidden or 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
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.
Take insecure/verify/cacert parameter from clouds.yaml and pass it to boto3.resource.
If insecure is True or verify is False use verify=False also for boto3.
Else, if you provide cacert(via cacert or verify parameter) it is also used for boto3.
If nothing from above is met, use verify=None to keep default boto3 behaviour.