Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Migrate Devel needs some work to get ready for Drupal 9, and Drush 9/10.
Also, recent 8.x-3.x versions of the Devel module cause Migrate Devel to break.
Proposed resolution
- Roll a stable (and hopefully final) release of Migrate Devel 8.x-1.0
- Open an 8.x-2.x branch for compatibility with Drupal 9, Drush 9+, and Devel 8.x-3.x
Final version of 8.x-1.x
- DONE. Opt-in to security advisory policy.
- #3037456: Dependency namespacing in .info.yml file
- DONE. Release migrate_devel 8.x-1.0
- DONE. Release migrate_devel 8.x-1.2
- #3150974: Add a basic composer.json to migrate_devel
- DONE. Mark it incompatible with Drush 9 and Drupal 9 (use composer conflict).
- DONE. Release migrate_devel 8.x-1.3
- #3151602: Invalid json in composer.json
Roadmap for 8.x-2.0
Must-haves
- DONE. Open an 8.x-2.x branch, enable dev releases.
- #3150974: Add a basic composer.json to migrate_devel
- #2938677: Make migrate:import --migrate-debug compatible with Drush9+
- DONE. Use the composer conflict key to assert that it can't work with Drush 8
- #3114943: Use Symfony Var-dumper instead of Kint
- #3136003: Add D9 core_version_requirement
- DONE. Release migrate_devel 8.x-2.0-alpha1
- #3310624: D10 Readiness
Should-haves, and/or could-haves
- #3153729: Remove dependency on devel module
- #3151276: Improve Symfony VarDumper appearance in Migrate Devel
- Consider dropping the integration with Configuration Update Manager module. Instead let users decide whether they prefer to use Configuration Update Manager or Configuration Development module. It's an opportunity to reduce the long-term maintenance needed for this module. Both of those modules are actively maintained and have more users than Migrate Devel does. #3377904: Remove legacy Drush 8 code and integration with config_update
- #3150978: Update migrate_devel project page
- Remove legacy code which was there for Drush 8 #3377904: Remove legacy Drush 8 code and integration with config_update
Comments
Comment #2
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedI 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.
Comment #3
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #4
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #5
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #6
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #7
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #8
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #9
jcnventura CreditAttribution: jcnventura at 1xINTERNET commented@andrewmacpherson, can you please re-release 1.0 as 1.2? Anyone that had "^1.2" or "^1.2@beta" in their composer.json will not be downgraded to the newer 1.0. It's strange to break semantic versioning like this.
Considering that 1.0 is already compatible with Drupal 9 (but not with Drush 9...), would it be possible to merge #3136003: Add D9 core_version_requirement in the 1.x branch before creating the 1.2 release?
Comment #10
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedGood 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.
Comment #11
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedI'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.
Comment #12
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #13
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #14
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #15
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #16
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedI 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...
drush migrate:status --migrate-debug
.I'm leaning towards (2) today, because:
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 thedrush config:devel-import <my_module>
ordrush 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.config:revert
,config:revert-multiple
, andconfig:import-missing
, and those manual commands will still be available if the integration is removed from Migrate Devel.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.
Comment #20
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedNew releases:
drush migrate:import --migrate-debug
is ready.Comment #21
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #22
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #23
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #24
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedComment #25
steinmb CreditAttribution: steinmb as a volunteer commentedAdding in the need for Drupal 10 support.
Comment #26
batigolixComment #27
batigolixComment #28
batigolixThe issues mentioned in this roadmap have all (or almost all) been addressed.