Module Description
The Configuration Update Manager project contains a base module and a reporting module.
Use the base module if another project has it as a dependency (example: Features).
The report module supplements the core Configuration Manager module, by providing a report that allows you to see the differences between the configuration items provided by the current versions of your installed modules, themes, and install profile, and the configuration on your site. The report is available from the administration UI, or via Drush commands.
If you run the report from the administration UI, you can also import new configuration provided by updates, delete unwanted configuration items, and revert your site configuration to the provided values, on a case-by-case basis.
The main use case is: You update a module, and it has either changed default config that it provides, or added new config items. You want to be able to import the new items, view the differences between the site config and the changed config, and possibly "revert" (or it may be an update) to the newly-provided default config.
This module is related to several existing issues:
* Help topics module: #2371439: Figure out what to do when module updates configurable topic
* Core Views/Views UI module: #1790398: Re introduce revert functionality for views using the config system
* Core Tour module: #1924202: Tour tips are provided as configuration, so never get updated
* Generic problem in config in Core: #1398040: Detect if default configuration of a module has been changed, and allow to restore to the original, #1497268: Add revert functionality to Config entities, and related issues
* Improving Core: #2957423: Proposal: Configuration Management 2.0 initiative
Other configuration-related contrib modules
* Configuration Tools: Facilitates storing your active config in files instead of the database.
* Configuration Split: Supports deploying a subset of your site configuration between sites
* Features: In Drupal 8, Features is basically a configuration packager. I have heard that this module be deprecated in favor of Configuration Split, but I am not sure.
* Configuration Development: A developer module that automatically imports/exports config at every page request, and allows you to export configuration in bulk into modules
* Configuration Synchronizer: Provides methods for safely importing site configuration from updated modules and themes.
Use the base module if another project has it as a dependency (example: Features).
The report module supplements the core Configuration Manager module, by providing a report that allows you to see the differences between the configuration items provided by the current versions of your installed modules, themes, and install profile, and the configuration on your site. The report is available from the administration UI, or via Drush commands.
If you run the report from the administration UI, you can also import new configuration provided by updates, delete unwanted configuration items, and revert your site configuration to the provided values, on a case-by-case basis.
The main use case is: You update a module, and it has either changed default config that it provides, or added new config items. You want to be able to import the new items, view the differences between the site config and the changed config, and possibly "revert" (or it may be an update) to the newly-provided default config.
This module is related to several existing issues:
* Help topics module: #2371439: Figure out what to do when module updates configurable topic
* Core Views/Views UI module: #1790398: Re introduce revert functionality for views using the config system
* Core Tour module: #1924202: Tour tips are provided as configuration, so never get updated
* Generic problem in config in Core: #1398040: Detect if default configuration of a module has been changed, and allow to restore to the original, #1497268: Add revert functionality to Config entities, and related issues
* Improving Core: #2957423: Proposal: Configuration Management 2.0 initiative
Other configuration-related contrib modules
* Configuration Tools: Facilitates storing your active config in files instead of the database.
* Configuration Split: Supports deploying a subset of your site configuration between sites
* Features: In Drupal 8, Features is basically a configuration packager. I have heard that this module be deprecated in favor of Configuration Split, but I am not sure.
* Configuration Development: A developer module that automatically imports/exports config at every page request, and allows you to export configuration in bulk into modules
* Configuration Synchronizer: Provides methods for safely importing site configuration from updated modules and themes.
Module Link
Project Usage
61781
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
The Configuration Update Manager project aims to solve the problem of easily importing new configuration, viewing differences between site config and changed config, and reverting to default config provided by module updates.
Data Name
config_update
OPENAI CHATBOT
OPENAI CHATBOT
