Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The Migrate UI has the ability to run a migration if it stops in the middle - we should test this.
Comments
Comment #2
alexpottComment #4
benjy CreditAttribution: benjy at PreviousNext commentedI personally think that we've always built the upgrade path to be run against a clean install. I don't much like the rollback for the upgrade path and I don't think we should support re-running migrations either.
Comment #5
heddnIs this a question of re-running a failed migration or just re-running a migration to pick up new data from the source system. If it is the later, I already know of folks who are doing this on D7=>D8 migrations since they haven't gone live yet with the new site. And traditionally using a highwater mark and sucking in new, unmigrated data is a huge win for migrate, especially when dealing with contrib scenarios where the data doesn't come from previous versions of Drupal.
Comment #6
benjy CreditAttribution: benjy at PreviousNext commentedheddn, I absolutely agree that the migrate api is used for the second scenario you describe however I believe this issue is in the context of the 1 click upgrade path and failed migrations.
Comment #7
heddnComment #8
heddnIn the case of re-running the automated migration that is provided inside core, I don't know that it is really a possibility since we don't really store the db credentials anywhere. Can this be marked Won't Fix?
Comment #11
mikeryanThere isn't currently any ability to rerun a migration through the core UI (failed or not) - postponing on #2687843: Add back incremental migrations through the UI.
Comment #14
heddnThis is no longer blocked.
Comment #25
quietone CreditAttribution: quietone at PreviousNext commentedThis issue was discussed at a migrate meeting on 30 July New Zealand Standard time, by mikelutz, benjifisher and myself (all migrate maintainers). It was pointed out when the migration fails it is expected that one restarts from an empty database, that there has been little support for this issue (more bumps than actual work) and there is also the point raised in #8. Base on that we all agreed to close this issue.