- Issue created by @DamienMcKenna
Rolling back a migration that has a destination of "user_data" does not work.
Create a custom migration that has a destination of "user_data".
Migrate the data.
Confirm the data was migrated correctly.
Rollback the migration using the command "drush migrate:rollback".
Expected outcome:
* The migrated data is removed.
Actual outcome:
* The migrated data is still present in the database.
Allow data that is migrated into user_data to be removed when the "drush migrate:rollback" command is executed in Migrate Tools.
Work out the cause of the problem.
Rolling back a migration to the user_data table deletes the data.
TBD
TBD
TBD
Active
11.0 π₯