- Issue created by @tstoeckler
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.
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.
?
?
?
Active
2.0
Code