Re-use SSL-related options from passed in Session
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-swiftclient |
New
|
Undecided
|
Unassigned | ||
Bug Description
Currently swiftclient already accepts keystoneauth Session object on instantiation.
However it is used only to fetch the token from Keystone, and further connection to Swift itself does not use this Session object.
Thus the SSL-related options that are present in the Session object (like cacert, verify etc) are ignored when establishing the connection to Swift, which effectively requires them to be passed explicitly even when they are already part of the Session object (example of a workaround [0]).
Ideally swiftclient should implement a ksa.Adpater-based Session client, but that would be a much biiger change.
The minimal change would be to use SSL-related options from Session object as defaults if Session has been specified during client instantiation.
