Found by alexpott on https://drupal.org/node/2003966#comment-7866263
- Module A provides some default configuration, to be enabled when module B is enabled.
- The default configuration references a plugin owned by module C
- Module C is not enabled when either module A or module B are
- The default configuration is installed, and is immediately broken - in Views it'd be a broken handler, some other systems can't handle it at all.
We should probably not install the configuration, if it's going to be invalid as soon as it's installed. That'd make this one a counterpart to- certainly the validation in there is going to be necessary for whatever happens here.
A couple of options then:
- skip the configuration install silently. This brings up the question of whether that configuration will ever get installed (i.e. if module C is enabled we're not going to look for configuration files in module A just in case they have a plugin owned by module C.
- prompt the person enabling the module to see if they'd also like to enable module C at the same time, then they can answer yes or know and we forget about this config file after that.