Config Import - Delete Entities
This module helps resolve configuration import errors that occur when entities need to be deleted before an entity type can be removed. It can automatically delete these entities to allow configuration imports to proceed or provide a debugging mode to list the entities that require deletion.
Introduction
Configuration management in D8 is amazing, and saves us a lot of effort. But one annoying thing is when it complains about entities that need to be deleted before a bundle/content-type/entity-type is deleted. When that happens, you cannot import any configurations until you've manually deleted the aforementioned entities.
This can be a problem if this happen during an automated configuration import as part of deployment (or similar). And it can when switching between branches on a project (where each project may have an entity type not on other branches yet), and when deploying changes with systems like Jenkins.
It may also not be trivial to find the entities and delete them (depending on what type of entities they are).
Enter this module
This module offers the option of automatically deleting these entities when detected, allowing the import of configurations to carry on.
It also offers a "debugging" mode in which it will list the entities that will/need to be deleted (as entity type/id pairs).
Both of these features can be independently enabled/disabled to fit your needs.