Store migrate overrides as config entities to allow single content entity config override

Open on Drupal.org →

Created on 29 July 2021, over 3 years ago

Updated 3 November 2023, about 1 year ago

Problem/Motivation

We are unable to encapsulate content type feature modules with this functionality.

Steps to reproduce

Create a Baseball Card content type, store its config exports in its own baseball_card module (easy to do with Features module).
Create a Pokemon Card content type, store its config exports in its own pokemon_card module.
Enable migrate overrides for each content type.
Export and store a Migrate Override configuration in one or the other, or in a mutual dependency.

The Migrate Override will not allow you to apply overrides to both content types once you've enabled both modules.

Proposed resolution

Use Config Entities to store content-type-specific migrate overrides individually.

Be able to export individual configurations, such as migrate_override.node.article.yml.

Remaining tasks

Update tests.
Add an update hook to deal with schema change or release major version.

User interface changes

Create a Migration overrides list page with an "Add Migrate override" button.
From the list page, a user will have the option to Delete or Edit a Migrate override.
Create a Migration override form with fields to:
- Enable a Migrate override via checkbox
- Select a content-type entity
- Select a bundle (if any)
- Select a field override option (Ignore this field, Prevent this field from being overwritten, or Allow this field to be overridden)

API changes

The service will need to be modified to capture the supplied migrate_override configurations. The configuration entity name would be something like migrate_override.node.baseball_card.

Data model changes

A Migrate override config entity will be needed.

✨ Feature request

Status

Needs work

Version

2.0

Component

User interface

Created by

🇺🇸United States jcandan

Live updates comments and jobs are added and updated live.

Incomplete comments

Merge Requests

!1Store migrate overrides as config entities to allow single content entity config override
Open
🇺🇸United States jcandan
updated 11 months ago

Comments & Activities

Not all content is available!

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

Merge request !1Issue #3225959: Store migrate overrides as config entities to allow single content entity config override → (Open) created by jcandan
Comment about 1 year ago →
🇺🇸United States jcandan
Would the maintainer be open to opening major release dev branch with this change?

It would be an opportunity to remove the 8.x-x.x version prefix and begin support for Drupal 10+.
Comment about 1 year ago →
🇺🇸United States mikelutz Michigan, USA
2.0.x branch is open now, and updated for D10. I'll probably drop an alpha with just the d10 fixes, but if you still want to work on this, we can include it in a beta.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024