On 27/03/14 18:11, Jay Dobies wrote:
It might be good to do a similar thing as Keystone does. We could keep
python-tuskarclient focused only on Python bindings for Tuskar (but keep
whatever CLI we already implemented there, for backwards compatibility),
and implement CLI as a plugin to OpenStackClient. E.g. when you want to
access Keystone v3 API features (e.g. domains resource), then
python-keystoneclient provides only Python bindings, it no longer
provides CLI.
+1
+1 also, I completely agree and almost brought this up but wanted to
stick on the topic of names. So essentially one standard python-*client
named after the API with only bindings and another CLI client named
after the UI.
Dougal
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
