Problem/Motivation

Due to things like: #2748609: [meta] Preserving auto-increment IDs on migration is fragile we should *always* use the migration process plugin instead of just assuming that the entity id will be provided.

Proposed resolution

Use migration process plugin, always.

Remaining tasks

  1. Collect/review the list of places where we don't use the migration process plugin.
  2. Then create a patch that switches all the migration process plugin.

User interface changes

API changes

Data model changes

Comments

heddn created an issue. See original summary.

heddn’s picture

heddn
Primary language English
Location Nicaragua
commented
Related issues: +#2748609: [meta] Preserving auto-increment IDs on migration is fragile
chx’s picture

chx commented

I really don't want to post to the core queue any more but: I decided to not do this because it's hard / impossible to tell where some IDs might be hardwired. Links in text, path aliases, IDs in configuration, anything goes. You need to decide what migrate_drupal is. Continuous migrations were not in the mandate I got. A faithful replication of Drupal 6/7 sites were.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

True, it is difficult to handle every case. But it doesn't hurt (well, some performance impact) to do all we can - it will all still work when preserving IDs, and handling at least the 90+% of straight-forward cases will significantly ease the burden for those consumers of the core migrations who are not preserving IDs (i.e., virtually everyone customizing their Drupal-to-Drupal migration paths).

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

heddn’s picture

heddn
Primary language English
Location Nicaragua
commented
Status: Active » Closed (won't fix)

This is over ambitious and won't get fixed this way. We're fixing these as we find them.