Remove implicit dependency on migrate_upgrade generated migrations

Created on 28 January 2025, 28 days ago

While there is no a hard dependency on the https://www.drupal.org/project/migrate_upgrade → module, the field-related migrations altered by this module expect the plugins IDs to match those generated by Migrate Upgrade. Namely:

For Drupal 7: upgrade_d7_field, upgrade_d7_field_instance, upgrade_d7_field_formatter_settings, upgrade_d7_field_instance_widget_settings.
For Drupal 6: upgrade_d6_field, upgrade_d6_field_formatter_settings, upgrade_d6_field_instance_widget_settings.

For more flexibility, allow the migrations' plugins IDs to be defined via settings. If no value is provided, fallback to the names listed above.

📌 Task

Status

Active

Version

1.0

Component

Code

Created by

🇳🇮Nicaragua dinarcon

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @dinarcon
Comment 28 days ago →
🇬🇧United Kingdom headbank
Just to be clear, do you still expect the migrations to be those generated by migrate_upgrade, or do you look to broaden the scope?

If you restrict to migrate_upgrade's migrations, then I would suggest that the naming not be entirely freeform, as a way of soft-enforcing this (it would be sensible to make that point clear in README.md as well). The drush command allows to specify a prefix ("upgrade_" is the default) so that could be the same setting you offer, while requiring the rest of the ID to match.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024