Roadmap for Migrate Devel 8.x-2.x

I recently wrote to the maintainer (@derimagia) offering to co-maintain this module, and outlined this plan to them.

@dermagia has now added me as a co-maintainer here.

I've been using the patches from #2938677: Make migrate:import --migrate-debug compatible with Drush9+ and #3114943: Use Symfony Var-dumper instead of Kint and the module is working well, so I expect to commit those soon.

Good catch on the 1.0 vs ^1.2 problem. I rushed that out too quickly last night. I have tagged a new 8.x-1.2 release today, because that was urgent.

I'll comment on the D9 compatibility issue too.

I'm aiming for a d9-compatible 2.x release in the next few days. The main issues already have patches RTBC or done-just-enough.

I think enough has been fixed for an 8.x-2.0-alpha1 release.

The "reset migrations" and "re-import migration config" features haven't been ported yet. I'm still pondering that. These two actions both happen at the same time, but to me they are separate things. I'm wondering about...

1. Ditch all of the drush migrate:status --migrate-debug.
2. Keep the reset part, but ditch the config import.
3. Treat the reset and config-import as two separate options.
4. ... or something else.

I'm leaning towards (2) today, because:

• I never actually used the drush migrate-status --migrate-debug feature. Typically I've been using the Configuration Development module, which doens't have any intergration with Migrate Devel. I run the drush config:devel-import <my_module> or drush config:devel-import-one <path-to-config-yaml-file> at whim. (Configuration Development module also has an auto-import feature, but it doesn't work with Drush migrate commands. See #2629284: drush migrate support.
• Meanwhile the Configuration Update Manager project also provides Drush commands for things like config:revert, config:revert-multiple, and config:import-missing, and those manual commands will still be available if the integration is removed from Migrate Devel.
• Without either of these modules, Drush itself allows drush config-import --partial --source=
/config/install.

So rather than maintain wrappers around other module's features, this module could be leaner, and just let users pick whichever configuration import tools they prefer. Some developers write their own wrappers Drush scripts, Robo commands, and whatnot.

Whatever I end up doing, it'll be best to decide before calling it a 2.x beta release.

New releases:

• migrate_devel 8.x-2.0-alpha1. The main use case of drush migrate:import --migrate-debug is ready.
• migrate_devel 8.x-1.3. Composer conflicts now prevent this being installed with Drush 8. Hopefully this was the "final-final" release :-)