swagger_client uses PoolManager from urllib3. PoolManager keeps the
connection_pool_kw passed during the init time and uses the same later
while initiating HTTPSConnection. Existing implementation instantiates
RESTClientObject() at import time, without giving an option to pass
the security parameters, viz. key_file, ca_certs etc. So we needed to
change the way instantiation/initialization was happening.
(copied from I3b490bbb47eb5f961951708dabe6c1abfbcece4e)
Change-Id: I6df227bcd030cb8c374bc83bb44dfea980c893b3
eval will execute a function before it has been determined to be
a python data type. Instead, use ast.literal_eval which validates
the object is a data type before executing it.
See:
http://nedbatchelder.com/blog/201206/eval_really_is_dangerous.html
(copied from Ia3d74747e66d72e97a3fb9029bd51331c902f874)
Change-Id: Iae0d42f8d14f66d6ea6cf2201646d8a796cc0cc9
Update to Kubernetes 1.2.2 version
Fixes to v1.json:
* Change 'any' types to 'object'
Fixes to rest.py:
* Fix __init__ to accept ca_certs
Change-Id: I190f26fac76480bc59ea5ceab7f1c94f16059086
