Hi,
Going back to the original message, how do you think we should proceed
with this bug? (https://review.openstack.org/#/c/55588/). Shall a new one
be created to remove the deprecated environment variables in all clients?
Thanks
Cristian
On 11/11/13 16:56, Kevin L. Mitchell
On Sat, 2013-11-09 at 14:14 +0800, Sam Morrison wrote:
I think you need to do option 2 and print deprecation warnings, then the
question becomes for how long.
I think there is a policy for this and that it is deprecate in N remove in N+1
Clients are a bit different so maybe keep it for ~6
On Mon, Nov 11, 2013 at 12:46 PM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
The thing here is, these environment variables have already been
deprecated for quite some time. The question is, have they been
deprecated long enough that we're clear to drop them entirely?
I say yes,
I think you need to do option 2 and print deprecation warnings, then the
question becomes for how long.
I think there is a policy for this and that it is deprecate in N remove in N+1
Clients are a bit different so maybe keep it for ~6 months?
Sam
On 8 Nov 2013, at 10:49 am, Leandro
Hi all,
Clients like python-novaclient/cinderclient/trove still support NOVA_*,
CINDER_*, TROVE_* variables for
backward compatibility support,while clients like
python-neutronclient/keystoneclient only supports OS_* env vars.
The following bug (#1061491, see review), mentions that it may be
