Skip to content

Fix handling of self-signed certs in s3_conn#1141

Open
chess-knight wants to merge 1 commit intomainfrom
fix/s3_conn
Open

Fix handling of self-signed certs in s3_conn#1141
chess-knight wants to merge 1 commit intomainfrom
fix/s3_conn

Conversation

@chess-knight
Copy link
Copy Markdown
Member

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.

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>
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.

1 participant