Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

2018-01-26 Thread Michael Johnson
Should be no issues with python-octaviaclient, we do not use the short options. Michael On Fri, Jan 26, 2018 at 1:03 PM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: >> We've been working this week to resolve an issue between

Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

2018-01-26 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: > We've been working this week to resolve an issue between cliff and > barbicanclient due to a collision in the option namespace [0]. > Barbicanclient was using the -s option, and then cliff's lister > command base class added

[openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

2018-01-18 Thread Doug Hellmann
We've been working this week to resolve an issue between cliff and barbicanclient due to a collision in the option namespace [0]. Barbicanclient was using the -s option, and then cliff's lister command base class added that option as an alias for sort-columns. The first attempt at resolving the