Details
-
Story
-
Resolution: Fixed
-
Medium
-
None
-
[4.0] - Sprint 5
Description
When calling migration command in Migration Bundle, migrations that are being executed should be stored in database in a similar manner that Doctrine Migrations do.
This includes:
- Not executing migrations that are already stored.
- Storing which Step caused the migration to fail, in case of retry - so that migration steps before it can be omitted.
- Allowing the current migration state to be accessed and displayed, at least using a dedicated status command.