0c90b740cc
The __future__ module [1] was used in this context to ensure compatibility between python 2 and python 3. We previously dropped the support of python 2.7 [2] and now we only support python 3 so we don't need to continue to use this module and the imports listed below. Imports commonly used and their related PEPs: - `division` is related to PEP 238 [3] - `print_function` is related to PEP 3105 [4] - `unicode_literals` is related to PEP 3112 [5] - `with_statement` is related to PEP 343 [6] - `absolute_import` is related to PEP 328 [7] [1] https://docs.python.org/3/library/__future__.html [2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html [3] https://www.python.org/dev/peps/pep-0238 [4] https://www.python.org/dev/peps/pep-3105 [5] https://www.python.org/dev/peps/pep-3112 [6] https://www.python.org/dev/peps/pep-0343 [7] https://www.python.org/dev/peps/pep-0328 Change-Id: I739502c3379364aafd2363c09d9a8d539100bf44 |
||
|---|---|---|
| .. | ||
| versions | ||
| README | ||
| __init__.py | ||
| env.py | ||
| script.py.mako | ||
README
The migrations in `alembic_migrations/versions` contain the changes needed to migrate between Vitrage database revisions. A migration occurs by executing a script that details the changes needed to upgrade the database. The migration scripts are ordered so that multiple scripts can run sequentially. The scripts are executed by Vitrage's migration wrapper which uses the Alembic library to manage the migration. Vitrage supports migration from Train release or later. Please see https://alembic.readthedocs.org/en/latest/index.html for general documentation To create alembic migrations use: $ vitrage-dbsync-revision --message --autogenerate Stamp db with most recent migration version, without actually running migrations $ vitrage-dbsync-stamp --revision head Upgrade can be performed by: $ vitrage-dbsync - for backward compatibility $ vitrage-dbsync --revision head