You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @crydotsnake stated out, we have no "node migration status" in Neos 9.0 anymore.
In general this was a useful feature to check if node migrations had already applied or not. But due to the changes in the node migration we can't guarantee anymore, that a migration really got applied to the content. E.g. a migration could be applied to a review workspace and partially or fully reverted.
Is it worth to store the migration executions nevertheless?
The text was updated successfully, but these errors were encountered:
We decided in our weekly to skip this for now as it can get quite complex (we need to store CR instance, affected content streams and there are potential issues with eventual consistency). Also it is relatively easy to work around this issue with 3rd party packages, for example https://github.com/swisscomeventandmedia/Swisscom.CommandMigration
#4442 (comment)
As @crydotsnake stated out, we have no "node migration status" in Neos 9.0 anymore.
In general this was a useful feature to check if node migrations had already applied or not. But due to the changes in the node migration we can't guarantee anymore, that a migration really got applied to the content. E.g. a migration could be applied to a review workspace and partially or fully reverted.
Is it worth to store the migration executions nevertheless?
The text was updated successfully, but these errors were encountered: