History

Stephen Finucane 64621053c2 db: Migrate to alembic This is significantly easier than Cinder, Nova etc. as Heat hasn't had any database migrations in multiple cycles, meaning we don't need to worry about having to apply any older sqlalchemy-migrate migrations before switching to alembic. Instead, we simply need to determine we're upgrading a deployment that was previously using sqlalchemy-migrate, upgrading a deployment that has already migrated to alembic, or deploying a new deployment, adjusting accordingly. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Change-Id: I808af9cb21ba21808209b1daddac7426f4cad310		2023-03-25 12:00:35 +09:00
..
versions	db: Sync alembic, sqlalchemy-migrate migrations	2023-03-23 11:01:07 +00:00
README.rst	db: Add initial alembic configuration	2023-03-23 11:01:07 +00:00
env.py	db: Migrate to alembic	2023-03-25 12:00:35 +09:00
script.py.mako	db: Add initial alembic configuration	2023-03-23 11:01:07 +00:00

README.rst

Database migrations

This directory contains migrations for the database. These are implemented using alembic, a lightweight database migration tool designed for usage with SQLAlchemy.

The best place to start understanding Alembic is with its own tutorial. You can also play around with the alembic command:

$ alembic --help