openstack
/
coverage2sql
Code Issues Proposed changes

Fix coverage2sql-db-manage usage document 

This commit fixes coverage2sql-db-manage usage in README.rst. We can't
use use --database-connection option now. So this commit just removes
the description. We may add the option in the future, though.

Change-Id: I6018fc5cf394c99ccf5f57bb33f30a21eab7456b
This commit is contained in:
Masayuki Igawa 2017-02-03 16:50:00 +09:00
parent ff8f03ece5
commit 89186aa5d5
No known key found for this signature in database
GPG Key ID: 251CCDE9053850E4
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.rst
View File

@ -30,15 +30,11 @@ DB Setup
The usage of coverage2sql is split into 2 stages. First you need to prepare a
database with the proper schema; coverage2sql-db-manage should be used to do
this. The utility requires db connection info which can be specified on the
command or with a config file. Obviously the sql connector type, user,
this. The utility requires db connection info which can be specified with a
config file. Obviously the sql connector type, user,
password, address, and database name should be specific to your environment.
coverage2sql-db-manage will use alembic to setup the db schema. You can run the
db migrations with the command::
coverage2sql-db-manage --database-connection mysql://coverage:pass@127.0.0.1/coverage upgrade head
or with a config file::
db migrations with a config file::
coverage2sql-db-manage --config-file etc/coverage2sql.conf upgrade head