openstack/python-keystoneclient
Code Issues Proposed changes

Make use_keyring False by default.

Browse Source 
Updates the use_keyring option for the Keystone Client class
to default to False by default. This provides for a much
easier upgrade path the the most recent keystone-client code
and is backwards compatible with the previous release.

This does not change the default of the no_cache keystone CLI
which will still enable use_keyring by default.

Fixes LP Bug #1087434.

Change-Id: Iaafadde660b0542a9c0a9c1bb742cb369b523a68
This commit is contained in:
Dan Prince
2012-12-06 15:26:46 -05:00
parent 1bff1909df
commit 93d243147e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
keystoneclient/client.py
View File

@@ -50,7 +50,7 @@ class HTTPClient(httplib2.Http):
password=None, auth_url=None, region_name=None, timeout=None,
endpoint=None, token=None, cacert=None, key=None,
cert=None, insecure=False, original_ip=None, debug=False,
auth_ref=None, use_keyring=True, force_new_token=False,
auth_ref=None, use_keyring=False, force_new_token=False,
stale_duration=None):
super(HTTPClient, self).__init__(timeout=timeout, ca_certs=cacert)
if cert: