This project is not covered by Drupal’s security advisory policy.

Config Exclude allows you to exclude modules and their configuration from being exported. It is an easy way for developers to enable development modules without the risk of accidentally exporting the enabled-state or their dependent config.

See #2926505: drush cex --skip-modules was removed in favor of config_split, but config_split is not feature-equivalent to understand why this module was created.

Usage

Enable the module and activate the filter by declaring $settings['config_exclude_modules'] in your settings.php file, eg:

$settings['config_exclude_modules'] = ['devel', 'stage_file_proxy'];

Now, when you export configuration (drush config-export), the selected modules should no longer show up in core.extension.yml and their configuration should not be exported.

Part of Drupal Core 8.8.0

This module was added to Drupal core 8.8.0, albeit in somewhat different form, as part of CMI 2.0. Special credits for this go to Fabian Bircher.

Drupal core uses the same syntax in settings.php as this module does, so if you are already using this module, you can simply upgrade to version 8.8 and disable and remove the contrib config_exclude module. Everything should continue working as before.

For more information, read the Change Record Modules can be excluded from the configuration synchronization or the blog post Highlights from CMI 2.0 in Drupal 8.8.0.

Supporting organizations: 
supports community contributions during office hours.

Project information

Releases