savanna-db-manage does not read /etc/savanna/savanna.conf by default
Bug #1202227 reported by
Matthew Farrellee
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
Wishlist
|
Sergey Lukjanov |
Bug Description
The savanna-db-manage tool only functions when provided --config-file (probably also --config-dir). it should search for /etc/savanna/
Changed in savanna: | |
status: | New → Triaged |
importance: | Undecided → Low |
milestone: | none → 0.2.1 |
tags: | added: 0.2.1 |
Changed in savanna: | |
milestone: | 0.2.1 → none |
tags: | removed: 0.2.1 |
Changed in savanna: | |
milestone: | none → 0.3a1 |
tags: | added: 0.3 |
Changed in savanna: | |
importance: | Low → Wishlist |
Changed in savanna: | |
milestone: | 0.3a1 → 0.3 |
Changed in savanna: | |
milestone: | 0.3 → next |
tags: | removed: 0.3 |
Changed in savanna: | |
milestone: | next → icehouse-3 |
Changed in savanna: | |
status: | Triaged → Invalid |
importance: | Wishlist → Undecided |
status: | Invalid → New |
Changed in savanna: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
assignee: | nobody → Sergey Lukjanov (slukjanov) |
Changed in savanna: | |
status: | Fix Committed → Fix Released |
Changed in sahara: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
AFAIK, {name}-db-migrate in other projects also expects --config-file parameter.
so, maybe, we can mark this as expected behaviour?