trove-manage db_wipe should be renamed to db_recreate
Bug #1286180 reported by
Ionuț Arțăriși
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Ionuț Arțăriși | ||
Bug Description
The trove-manage db_wipe command not only wipes the database, but it also recreates it afterward. It should be renamed to db_recreate to better reflect what it does.
| Changed in trove: | |
| assignee: | nobody → Ionuț Arțăriși (mapleoin) |
| status: | New → In Progress |
Revision history for this message
| Ionuț Arțăriși (mapleoin) wrote | #1 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| milestone: | none → icehouse-rc1 |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | icehouse-rc1 → 2014.1 |
To post a comment you must log in.
This was fixed in commit: a5d745dd8717de4
Review link: https:/