ModelsMigrationsSync barks on custom alembic_version table
Bug #1558116 reported by
Yuriy Taraday
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.db |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
I use different name for alembic_version table.
In tests my db_sync command will use some custom config with different 'version_table' setting, but to get a difference between models and tables generated by migrations ModelsMigration
It looks like test case should either have a hook to return all config that is used to interact with Alembic or at least to allow user to specify 'version_table' setting somehow.
Changed in oslo.db: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
To post a comment you must log in.