db-migrate

To apply database migrations safely, use Alembic upgrades for manager, accountmgr, and appproxy databases, enforcing pre-flight checks to validate status and ensure consistency before applying pending changes to the target head revision.

Yes, you can rollback Alembic database migrations by performing targeted downgrades to a specific revision, ensuring safe and auditable schema reversions across manager, accountmgr, and appproxy databases when needed.

Checking database migration status before upgrading involves running pre-flight validation checks on the manager, accountmgr, and appproxy databases to verify consistency and identify pending schema changes prior to deployment.

Yes, Backend.AI supports automated schema migrations across multiple databases, orchestrating Alembic upgrade and downgrade operations for manager, accountmgr, and appproxy components while enforcing pre-flight checks for safe, auditable migrations.

Database downgrade operations are needed when rolling back schema changes after pulling new migrations, allowing targeted revisions and backups to safely revert manager, accountmgr, and appproxy databases to a previous consistent state.

Yes, pre-flight checks are required before applying Backend.AI database migrations to validate current database status, enforce consistency, and ensure safe, auditable upgrade and downgrade operations across all relevant components.