designate-manage does not migrate designate_pdns DB from PowerDNS 3.x to 4.x version DB Schema
Bug #1746836 reported by
Ritesh Anand
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
New
|
Undecided
|
Simon Leinen | ||
Bug Description
It seems that the way to go from PowerDNS version 3.x to PowerDNS version 4.x as a Designate backend is to do SQL import (of https:/
This seems to be a not very maintainable approach, as compared to a versioned DB migration approach.
Can designate-mange be adapted to handle this?
| Changed in designate: | |
| assignee: | nobody → Simon Leinen (simon-leinen) |
To post a comment you must log in.
