Problem/Motivation
Migrations are core are now plugins, not config entities. This module used to provide only the config entity list builders and forms on-top of that config entity, which now, no longer exists.
Proposed resolution
The config entity will be added to migrate_api in #2677196: Re-introduce migration config entity and then the UI can be re-worked to use a migration plugin as a template/starting point, and a way to create entire new migrations from the UI that will be shimmed into the plugin definitions.
Remaining tasks
Development
User interface changes
Yes, I imagine the migration you're starting from will be selected from the UI, or you can select non at all.
API changes
Yes, likely.
Data model changes
Yes, likely.
Comments
Comment #2
kevinquillen CreditAttribution: kevinquillen at Velir commentedHow can we help move the needle on this one?
Comment #3
benjy CreditAttribution: benjy at PreviousNext commentedThe module needs a rewrite, if someone wants to have a go, feel free to post patches here but I don't have the time for this module right now.
Comment #4
stBorchertTalked with @benjy yesterday and trying to start to work on this.
Comment #5
stBorchertWell, I guess I figured out why Ben noted, nobody wanted to update this :D
First patch makes at least some of the visible parts working again, so you can actually see something.
There are some points to discuss eventually:
* Do we need to create an instance of the migration on form rebuild or can we use simply an array with the configured values?
* It would be really (like "really"!) great, if migrate plugins would get a label. This could be used in the dropdown instead of the plugin ID (== more readable and meaningful to users).
* Would it make sense to list all available migrations on admin/config/migrate/migrations or only list the migrations created through the ui? In the latter case, would migrations need an additional flag?
more to come ;)
Comment #6
joelpittetThis patch does help get past the fatal but there is a bunch of commented code in there.
Not sure the answer to the questions though in #5
Comment #8
Summit CreditAttribution: Summit as a volunteer commentedHow about moving this to Drupal 10 now? Greetings,
Comment #9
kevinquillen CreditAttribution: kevinquillen at Velir commentedThis module has been marked unsupported and obsolete.