Commit 18e6d92
Fix handling of self-signed certs in s3_conn (#1141)
* Fix handling of self-signed certs in s3_conn
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>
* Simplify logic a bit and add documentation to code
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
* Take cacert from cacert parameter only, not from verify
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
* Rectify comment regarding boto3 default behavior
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
* Improve comment further
thanks @chess-knight!
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
---------
Signed-off-by: Roman Hros <roman.hros@dnation.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Co-authored-by: Matthias Büchse <matthias.buechse@alasca.cloud>1 parent 14237f6 commit 18e6d92
1 file changed
Lines changed: 12 additions & 5 deletions
Lines changed: 12 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
28 | 28 | | |
29 | 29 | | |
30 | 30 | | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
35 | 42 | | |
36 | | - | |
| 43 | + | |
37 | 44 | | |
38 | 45 | | |
39 | 46 | | |
| |||
0 commit comments