In [#8604729-100], some decision was taken around modules NOT cleaning up installed config entities when uninstalled.

Unfortunately, if you attempt to reinstall one of these modules, it will throw a Fatal error, even if its simply trying to provide the same config entity it left behind.

Proposed resolution

Remaining tasks

User interface changes

API changes


larowlan’s picture

Title: Reinstalling a module already providing config entities cases a Fatal » Reinstalling a module already providing config entities causes a Fatal
Issue tags: +Needs tests
xjm’s picture

Priority: Normal » Major
Issue tags: +Configuration system, +Configurables

@xtfer, can you provide a specific sequence of steps to reproduce this?

xjm’s picture

Actually, re-reading, this might also be the bug in the specific module. It should clean up its own stuff in hook_uninstall(). But STR will clarify. :)

xjm’s picture

Status: Active » Postponed (maintainer needs more info)

Better status.

alexpott’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

So this is now handled by config dependencies - if the configuration depends on the module it will be removed.

If the config entity provide by the module does not depend on the module then we handle this with the work done in #2140511: Configuration file name collisions silently ignored for default configuration.

There is a question around whether we should add an enforced dependencies on the module during configuration install but I think it's best to leave this up to the module author.