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

?

Issue fork config_overlay-3468137

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

tstoeckler created an issue. See original summary.

tstoeckler opened merge request !35

  • tstoeckler committed e3e57a4d on 2.x 
    Issue #3468137 by tstoeckler: Support config_overlay.deleted in a...
tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Active » Fixed
Related issues: +#3395781: Add a test with a profile with a config/sync directory

After #3395781: Add a test with a profile with a config/sync directory this was now fairly straightforward to write a test for.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.