I am trying to install a module on a higher level environment. The module installs configuration in its config/install directory, and that configuration was also exported to the main site configuration folder. On the upper environment, I cannot install the module now (configuration already exists). How do you support this case? Do you deploy the install first (core.extention.yml), then come in behind it with the additional config it exports to the normal Drupal configuration directory?

  • Did the module activation ship originally in core.extension?
    – mona lisa
    Jun 16, 2022 at 16:10
  • Nope - I just noticed that. I may have been bit by config_split again.
    – Kevin
    Jun 16, 2022 at 16:14

1 Answer 1


You have to remove the module’s exported config first then re-add it along with the module activation.

Technically all you have to do is remove the module’s configuration from active configuration, which you can do with Drush.

  • Yep, got bit by config_split. Didn't notice it did not export the module enable to core.extension.yml. This would also work.
    – Kevin
    Jun 16, 2022 at 18:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.