Remove plugin-specific migrations (and squash them)
As a part of activities for fixing Neutron DB's state, after 'healing it' by adding a specific 'fixing migration', we should look back at migration history and get rid of logic for making plugin-specific migrations.
As a bonus point we could use this chance to squash intra-release migrations for previous versions. After all DB migrations are not like git where having the full history is important.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- High
- Drafter:
- Salvatore Orlando
- Direction:
- Approved
- Assignee:
- Salvatore Orlando
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Kyle Mestery
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
20-July (mestery): Approving and marking as Juno-3.
Gerrit topic: https:/
Addressed by: https:/
Make Juno migrations config independent
Addressed by: https:/
Remove migration conditional logic from template
Addressed by: https:/
Heal downgrade
Addressed by: https:/
Introduce havana initial state
Addressed by: https:/
Heal script: Drop fks before operating on columns
Addressed by: https:/
Unconditional downgrade
Gerrit topic: https:/
Addressed by: https:/
Remove logic for conditional migrations
