Is your feature request related to a problem? Please describe.
There is no check about migration states on data dump from an archive against project that try to load it. Two projects can have the applications and similar configurations but have different migrations states.
Describe the solution you'd like
When loading, there could be a check process about migrations state.
For this, the archive manifest should include the migrations state (the last performed migration) for each applications.
Then the loader could compare and abort operation with an error.
This should be option, either optin or optout, but user should be able to disable checking.
Describe alternatives you've considered
Do not any check, the user should have to know its projects.
Is your feature request related to a problem? Please describe.
There is no check about migration states on data dump from an archive against project that try to load it. Two projects can have the applications and similar configurations but have different migrations states.
Describe the solution you'd like
When loading, there could be a check process about migrations state.
For this, the archive manifest should include the migrations state (the last performed migration) for each applications.
Then the loader could compare and abort operation with an error.
This should be option, either optin or optout, but user should be able to disable checking.
Describe alternatives you've considered
Do not any check, the user should have to know its projects.