Revisit and revive alembic migration logic
Registered by
John Wood
Work was completed a while ago on an Alembic based migration process. This blueprint is to get that logic working again. In particular, at time zero, the first Barbican app to run should populate the database tables and sync them to the latest Alembic version file ('head'). Thereafter, only more recent Alembic version files should be used to modify the database schema.
Blueprint information
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Revive Alembic-based database migration logic.
(?)