Problem/Motivation

If a module called foo has a config file called foo_more.bar.yml in its config/install directory and the foo_more.bar config does not have a dependencies array the ConfigInstaller will permit the module to be installed. This has several bad implications:

The configuration will not be cleaned up on uninstall

The configuration will not met dependency checks during configuration sync essentially making the active configuration undeployable.

Thanks to @OnkelTem whose questions in IRC led to the creation of this issue.

Proposed resolution

Fix ConfigImporter::validateDependencies() to check this.

Remaining tasks

User interface changes

None

API changes

No API changes but some contrib or custom modules might no longer be able to be installed. They will need to change the configuration name and write upgrade paths.