Support Migrate Tools' "includes" in migrations

Created on 26 January 2025, about 2 months ago

Problem/Motivation

Since #3250040: Shared configuration for migrations migrations may have a include key which reference shared configurations to avoid copy-paste in different migrations. Migrate Plus' migration configuration entities, however, do not currently support an include key.

Steps to reproduce

-

Proposed resolution

Add support for the include key.

Remaining tasks

-

User interface changes

-

API changes

-

Data model changes

Migrate Plus' migration configuration entities may contain an include key, just like other migrations.

Feature request
Status

Active

Version

6.0

Component

Plugins

Created by

🇩🇪Germany tstoeckler Essen, Germany

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

Merge Requests

Comments & Activities

  • Issue created by @tstoeckler
  • 🇩🇪Germany tstoeckler Essen, Germany

    Opened a quick MR with the minimum to get this working. I opted to place the include key right before source, process and destination as I would guess that those are the keys that will be mostly "included", but I'm not at all tied to the order.

  • Pipeline finished with Failed
    about 2 months ago
    Total: 459s
    #406649
  • 🇩🇪Germany tstoeckler Essen, Germany

    Ah, I didn't think about updating the example and test migrations to include the include key. Also will need an update path, I guess. Would love some confirmation, though, first that I'm on the right track with this before fixing the tests.

Production build 0.71.5 2024