Move destination_module from Migrate to Migrate Drupal

Created on 4 April 2024, about 1 year ago

Problem/Motivation

Follow up from πŸ“Œ Move source_module and destination_module from Migrate to Migrate Drupal Needs work

*Copied summary for source_module

The destination_module and destination_module are needed for Drupal and should not be in Migrate, they probably should be in Migrate Drupal. Let's see what needs to be done to get them out of Migrate.

Steps to reproduce

NA

Proposed resolution

TBD

Remaining tasks

Update summary

User interface changes

NA

API changes

TBD

Data model changes

TBD

Release notes snippet

TBD

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated 9 days ago

Created by

πŸ‡ΊπŸ‡ΈUnited States smustgrave

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

Comments & Activities

  • Issue created by @smustgrave
  • Status changed to Closed: won't fix about 1 month ago
  • πŸ‡³πŸ‡ΏNew Zealand quietone

    This was discussed on the Migrate video call today, benjifisher, heddn, mikelutz and myself were present. πŸ“Œ [meeting] Migrate Meeting 2025-04-24 2100Z Active

    The properties source_module and destination_module was added to support the Migrate Drupal UI. The source_module was specific to legacy Drupal module so it has been moved from Migrate to Migrate Drupal. However, destination_module refers to the modern Drupal module so there is no urgent need to remove it. Having in core does no harm, even if it becomes unused. So, this is a won't fix. Like always, that decision can be reviewed later.

    Right now, we want to put effort into removing Migrate Drupal and Migrate Drupal UI from core and improving the migrate ecosystem.

Production build 0.71.5 2024