Support for Migration derivers ?

Created on 18 July 2022, over 2 years ago
Updated 17 July 2023, over 1 year ago

Is it there support for derivers in migrate_plus migrations ?

I've tried adding a "deriver: XXX" item in my migration config files, and importing them. When i export them again, the deriver configuration field is removed.

In case that there is no support for derivers in place, what would it take to put this in place ?
In case that there is support for it, maybe writing some documentation about how to set it up, or writing some example module might be a good idea.

✨ Feature request
Status

Active

Version

6.0

Component

Documentation

Created by

πŸ‡ͺπŸ‡ΈSpain guiu.rocafort.ferrer Barcelona

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States euk

    I am surprised this didn't get any attention in a year or so...

    Same issue here - spent several hours on it and it appears Migrate Plus configurations do not support derivatives. Worth noting that it also appears Migrate Plus configurations are derivatives themselves. I end up writing standard migrations for some of the content I need to migrate.

  • πŸ‡ΊπŸ‡ΈUnited States euk
  • Status changed to Needs review 30 days ago
  • πŸ‡§πŸ‡ͺBelgium Frederikvho Belgium

    I know this an older issue, but I ran into this recently and wanted to document my solution in case anyone else runs into this.

    This is what solved it for me: I added the migration to my custom module's /migrations folder prior to enabling the module. I am guessing core's migration discovery discovers the deriver this way.
    Because now the config gets created, without deleting the deriver parameter.

    This was also good post for me: https://www.webomelette.com/dynamic-migrations-using-templates-drupal-8

Production build 0.71.5 2024