Michael Basnight fd43cbd73b Massive refactoring to the troveclient
The new client adheres to the standards of the other clients
now. It prints out tables, uses ENVVAR's for auth, no longer
stores pickled json in a login token, uses openstack common,
and moves the cli operations into a v1 module for the future
of trove when it has a v2 api.

Please note for compatibility, the troveclient.compat module
has the old cli. In order to deploy it, amend the setup.cfg
to include the compat module.

implements blueprint cli-compliance-upgrade

Change-Id: Ie69d9dbc75ce90496da316244c97acca1877a327
2013-10-09 19:21:08 -07:00
2013-06-18 00:05:22 -07:00
2013-06-21 20:15:23 +00:00
2013-06-21 20:15:23 +00:00
2013-06-21 20:15:23 +00:00

Python bindings to the Trove API

This is a client for the Trove API. There's a Python API (the troveclient module), and a command-line script (trove). Each implements 100% (or less ;) ) of the Trove API.

Command-line API

To use the command line API, first log in using your user name, api key, tenant, and appropriate auth url.

$ trove-cli --username=jsmith --apikey=abcdefg --tenant=12345 --auth_url=http://trove_auth:35357/v2.0/tokens auth login

At this point you will be authenticated and given a token, which is stored at ~/.apitoken. From there you can make other calls to the CLI.

TODO: Add docs

Description
OpenStack Database as a Service (Trove) Client
Readme 12 MiB
Languages
Python 99.8%
Shell 0.2%