Add back rollbacks on migrate_drupal_ui

Created on 15 March 2016, almost 9 years ago
Updated 19 August 2024, 6 months ago

Follow-up to #2687843: Add back incremental migrations through the UI

Problem/Motivation

Follow-up to #2683421: Remove incremental and rollback options from the UI (and add them back when they are more stable) which removes both the rollback and incremental options since they were untested and had several significant bugs. Unlike the incremental migration feature, rollback can probably be considered an additional feature and not necessarily block a stable Migrate UI.

Proposed resolution

Add back rollback migration support to the UI, with test coverage.

Only roll back content migrations, not configuration. This is because

  1. It is hard to roll back configuration reliably, since it can also be changed in other ways.
  2. It may be more useful to use the regular configuration management, after an initial migration, than to update, roll back, and re-run the configuration migrations.

Use the phrase 'incremental upgrade' instead of 'Rerun' as shown in the now dated screenshot. See #32

Check for NULL in core/modules/migrate/src/Plugin/migrate/destination/EntityConfigBase.php. This fixes a bug that was exposed by the new test coverage.

Add a link to Upgrade using web browser and update that page to describe the new option. Suggested text:

If an upgrade was not done then the Upgrade page provides information about the preparation steps that should be done before continuing with the upgrade. However, if an upgrade was done then you are asked if you want to import new configuration and content or to rollback the upgrade. If you continue, for any of these situations, you are then asked to define the source site.

Remaining tasks

  • Implement the new, reduced scope: only roll back content migrations.
  • Update the documentation in the handbook,

User interface changes

Before

After
Default is incremental

Selecting the Rollback


Druing rollback complete

Rollback complete

API changes

Depends on the solution.

Data model changes

None

Feature request
Status

Closed: won't fix

Version

11.0 🔥

Component
Migration 

Last updated about 1 hour ago

Created by

🇺🇸United States xjm

Live updates comments and jobs are added and updated live.
  • Needs product manager review

    It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

  • Needs release manager review

    It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024