Allow to transfer content even if migration states are different

[yvesgurcan]

Running npx migrations content --source-environment-id master --dest-environment-id non-master-env might result in an error like the following:

Error: Different migration states detected. master (1684445574618) !== non-master-env (1684445717917)

The command exits, which prevents from transferring any content, regardless of whether the model of the content to transfer is actually different between the two environments.

Would it be possible and reasonably safe to let users ignore the error and let them perform content transfers?

[bezoerb]

Hey @yvesgurcan,

i think it would be possible but i don't think that it's reasonably safe to do so. I could think of something like this:

Error: Different migration states detected. master (1684445574618) !== non-master-env (1684445717917)
Do you wish to:
a) run migrations on target environment
b) backup target environment and continue
c) ignore the risk and continue

But to be honest i think it's to risky and it isn't worth the effort of implementing this ;)
Maybe we should improve the error message to

Error: Different migration states detected. master (1684445574618) !== non-master-env (1684445717917)
Please run "npx migrations migrate -e master and try again"