database-migration

Idempotent database migrations fix Aurora MySQL schema drift by applying reconciliation patterns that safely run from any unknown state, using schema checks and a verification script to confirm the final state without destructive changes.

A reconciliation migration is a zero-downtime operation that achieves a consistent final schema from any intermediate state. You need it for production database drift when your Aurora MySQL schema has diverged and you must safely recover without data loss.

Yes, the skill uses pymysql as its dependency to execute verification scripts that query and confirm the final Aurora MySQL schema state, ensuring the applied database migrations resulted in the expected drift-free structure.

The best way to add a missing column safely is using an idempotent reconciliation migration pattern that checks if the column exists before adding it, followed by running the verification script to validate the final schema state.

Database migrations fail when run multiple times if they are not idempotent. This skill solves that by applying reconciliation migrations with schema checks that prevent duplicate operations, ensuring consistent execution without errors.