- Issue created by @dinarcon
Per the change record that introduces shared configuration → :
Share configuration for migrations has previously been handled via a migrate_group config entity provided by migrate_plus.
With the addition of shared configuration in Migrate tools, the use of groups is no longer needed.
The new shared configuration seems like the evolution of migration group. It would be appropriate for both systems to co-exists in the same module: Migrate Plus → .
Most of Migrate Tools functionality revolves around being a migration runner, either from the command line or from the UI.
Migrate Plus has historically extended the migration system with configuration entities, migration groups, more migration plugins, events, etc.
If someone feels comfortable using the migration runner included in Drush core and wanted to use the new shared configuration system, they would have to add a second runner to get access to the functionality. While Migrate Tools and Drush core offer almost the same interface, there are a good amount of differences. See 📌 Drush core migrate commands integration refactor Needs work
Move shared configuration functionality to the Migrate Plus module
Deprecate or remove the feature from Migrate Tools module
Get community feedback and agreement on the move
Deprecate or remove the feature from Migrate Tools module
Release major version of the modules as the move would be a breaking change
Move issues related to shared configuration from the Migrate Tools queue to the Migrate Plus one
Active
6.0
Code