Re-installing after un-installing config_overlay is not possible due to "config_overlay.deleted" being present in active config

Thanks for opening this issue!

To be perfectly honest, I was pretty confident that this was something with your particular setup, but I went ahead and tried to reproduce this and turns out it is absolutely reproducible. I am quite surprised, I guess I never re-installed the module before.

I guess somehow we mess with the config incorrectly so that when uninstalling the module, the config_overlay.deleted config is not properly deleted. Really strange, but definitely a critical bug. Will try to find some time to investigate this further.

For now, just attaching a file with my bash output for reproducing this. You can see that after uninstalling the module that the config_overlay.deleted.yml file gets exported and then the re-install fails.

So what happens is that when the module is uninstalled, config_overlay.deleted gets correctly deleted, but then Config Overlay's config subscriber detects that as a configuration deletion and adds config_overlay.deleted to the list of deleted configuration in config_overlay.deleted, in effect recreating the configuration.

This can be fixed, by simply ignoring this particular case in the config subscriber. Will push a branch with a fix and a test.

I noticed, though, that there is a similar problem in that Config Overlay adds the configuration names of other modules that are deleted to config_overlay.deleted as well. Will open an issue for that.

Thanks again!

Opened 🐛 Config of uninstalled modules gets recorded in config_overlay.deleted Active for the other issue. Will backport this one here to 1.x over there, since it's closely related.

Thus, marking this one as fixed.

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