List of configuration management modules
The following is a list of modules related to Drupal 8/9/10 Configuration Management which are actively maintained, in approximate order of popularity:
| Name | Machine name | Description |
|---|---|---|
| config_update | Provides an interface to review differences in your config between the YAML files and the database configuration storage. | |
| config_filter | Provides the ability to modify the configuration as it is synchronised between the database and the exported YAML files. | |
| config_split | Provides the ability to have different configuration in different environments. | |
| config_ignore | Allows configuration to be excluded from imports. | |
| config_readonly | Allows you to lock configuration changes done via the Drupal Admin UI. For example on a production server where config is exclusively managed via version control. | |
| config_devel | Allows automated import and export of configuration on each page load in development. Also allows a module to declare in its info file the configuration it is responsible for. | |
| config_rewrite | Allow the rewriting of pre-existing configuration at module installation time. | |
| config_inspector | Allows you to inspect configuration values and the use of schemas on top of them via the UI. Gives a developer and overview of configuration values. | |
| config_direct_save | Allows you to make automatic backups of your configurations and will allow direct syncing via the UI of configuration to files. | |
| config_selector | Allows modules and install profiles to provide multiple views of optional configuration that can be disabled and enabled dynamically on install. | |
| config_provider |
Provides a plugin type for extension-provided configuration to be used as a utility module by other modules. It includes support for the two core extension types, |
|
| config_partial_export | Allows the user to configure a partial export of configuration which will be exported to a tarball. | |
| config_export_ignore | Allows configuration to be ignore during exports. | |
| config_sync | Provides methods for safely importing site configuration from updated modules, themes, or distributions. | |
| config_actions | Provides a pluggable framework for easily manipulating configuration data via YAML files to create reusable software components. | |
| config_delete | Allow configuration items to be deleted via the UI. | |
| menu_link_config | Provides the ability to create and manage custom menu links as exportable configuration. | |
| config_snapshot | Enables snapshotting of extension-provided configuration. Supports updating configuration provided by modules, themes, and the install profile. | |
| config_merge | Provides a method for three-way merging of configuration items and a Config Filter plugin that safely merges configuration updates into the site's active configuration. | |
| config_distro | Provides a framework for managing configuration updates from distributions. | |
| config_normalizer |
This module can be used to wrap any configuration storage, creating a read-only version of the storage for which any data read will be returned in a normalized form. A common usage would be to minimize non-meaningful differences when comparing configuration data. |
|
| config_tools | Auto commits changes to your configuration to a specified git repository for every configuration change. | |
| config_override |
Allows overriding settings by either a site wide override folder specified by 'override' in your |
|
| config_log | This module allows to log any configuration change in Drupal 8. | |
| config_single_export | Alters the single item export form and adds an Export button to it to download the selected configuration. | |
| config_share | Enables commonly needed configuration items to be shared among multiple features and distributions. | |
| Webform Config Ignore | webform_config_ignore |
Webform Config Ignore adds a filter to configuration import and export to skip webforms and webform options. This allows site editors to change webforms and options lists on production without having their work obliterated on a new deployment. |
| Config Layers | config_layers |
Config Layers permits the import and export of configuration into multiple layers (each layer has a database storage and a corresponding file storage). Layers are merged and synchronized into the active configuration |
| Config Overview | config_overview |
The Configuration Overview module aims at helping to understand how is managed the configuration on synchronization. Thus it provides a page that indicates for each configuration if it is overridden, synchronized or protected on import. |
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion
