642dac165f
This API allowed users to abstract the differences between sqlalchemy-migrate and alembic. However, no one is using it for that and its continued existence necessitates continued support for sqlalchemy-migrate. Deprecate it now and encourage the odd user to switch to alembic directly. Change-Id: Ia5979369f23b38a2c7307f4112651a8bedb45c01 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
15 lines
709 B
YAML
15 lines
709 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The ``oslo_db.sqlalchemy.migration`` module is deprecated for removal.
|
|
It only supports ``sqlalchemy-migrate``, which is no longer under active
|
|
development and has been effectively replaced by ``alembic``. Users of
|
|
this module should consider switching to ``alembic`` or, if necessary,
|
|
using ``sqlalchemy-migrate`` directly.
|
|
- |
|
|
The ``oslo_db.sqlalchemy.migration_cli`` module is deprecated for removal.
|
|
It was intended to provide an abstraction layer over different migration
|
|
backends - specifically ``sqlalchemy-migrate`` and ``alembic`` - however,
|
|
takeup has been limited and its expected that users will use ``alembic``
|
|
directly nowadays.
|