config_overlay.deleted can no longer live in an install profile

Created on 14 August 2024, 11 months ago

Updated 5 June 2025, about 2 months ago

Problem/Motivation

This is a regression from the 8.x-1.x branch. When reading the config_overlay.deleted configuration, to determine the list of configuration not to overlay the transform subscriber has not yet been able to overlay the config_overlay.deleted configuration itself, in case it is not part of the config export directory.

Thus, it will not be considered as part of the import, so that the shipped configuration will be detected as "to be created when importing" even though it is explicitly marked as deleted.

Steps to reproduce

Delete a shipped configuration entity, and place the resulting config_overlay.deleted.yml in an install profile. Then attempt to import configuraiton. Config Overlay will incorrectly re-create the deleted configuration.

Proposed resolution

API changes

Data model changes

🐛 Bug report

Status

Active

Version

2.0

Component

Code

Created by

🇩🇪Germany tstoeckler Essen, Germany

Live updates comments and jobs are added and updated live.

Merge Requests

!35config_overlay.deleted can no longer live in an install profile
Merged
🇩🇪Germany tstoeckler
updated about 2 months ago

Comments & Activities

Issue created by @tstoeckler
Merge request !35Issue #3468137 by tstoeckler: Support config_overlay.deleted in a profile → (Merged) created by tstoeckler
Comment about 2 months ago →
System Message

tstoeckler → committed e3e57a4d on 2.x
Issue #3468137 by tstoeckler: Support config_overlay.deleted in a...
Comment about 2 months ago →
🇩🇪Germany tstoeckler Essen, Germany
After 📌 Add a test with a profile with a config/sync directory Postponed this was now fairly straightforward to write a test for.
Comment about 1 month ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024