Verify legacy migration completion
This commit is contained in:
@@ -43,6 +43,11 @@ Run in this order for local database workflows:
|
||||
5. Migrate legacy consumers:
|
||||
- `npm run db:migrate:legacy-consumers`
|
||||
|
||||
The migration command finishes with a cutover verification across the complete
|
||||
database. It exits with an error while any legacy consumer lacks a migration
|
||||
mapping, including consumers that cannot be migrated because they have no circuit
|
||||
list assignment. Do not remove or disable the legacy path until this check passes.
|
||||
|
||||
## Validation Checks
|
||||
|
||||
After migration, verify:
|
||||
@@ -72,6 +77,6 @@ Actions:
|
||||
|
||||
Do not delete legacy consumers yet.
|
||||
|
||||
- legacy endpoints/views may still depend on them
|
||||
- legacy endpoints/views remain enabled only until the cutover verification passes
|
||||
- migration trace tables reference old/new mapping
|
||||
- keeping legacy rows allows comparison and rollback validation during transition
|
||||
|
||||
Reference in New Issue
Block a user