Module Description
This module helps with developing configuration. Do not deploy in production environments. Exercise caution and always use version control.
It does three things:
* Automated import of configuration files into the active storage. At the beginning of every request the changed files are saved the way as if it were dumped in the core config module provided "Single import" form.
* Automated export of configuration objects into files. Only a list of filenames is required, the configuration object names are automatically derived. One configuration object can be auto exported into multiple files. This is the equivalent of copying the export from the 'Single export' screen.
* Helps creating modules that behave somewhat similarly to features export in Drupal 7. Under config_devel the module info yml should contain a list of config objects this module deals with then drush config-devel-export MODULE_NAME will write those config objects into the config/install directory of the module.
Typically filenames wil be something like modulename/config/install/foo.bar.yml.
Note: system.site, core.extension and simpletest.settings is not compatible with the auto import feature. This is very unlikely to be fixed.
It does three things:
* Automated import of configuration files into the active storage. At the beginning of every request the changed files are saved the way as if it were dumped in the core config module provided "Single import" form.
* Automated export of configuration objects into files. Only a list of filenames is required, the configuration object names are automatically derived. One configuration object can be auto exported into multiple files. This is the equivalent of copying the export from the 'Single export' screen.
* Helps creating modules that behave somewhat similarly to features export in Drupal 7. Under config_devel the module info yml should contain a list of config objects this module deals with then drush config-devel-export MODULE_NAME will write those config objects into the config/install directory of the module.
Typically filenames wil be something like modulename/config/install/foo.bar.yml.
Note: system.site, core.extension and simpletest.settings is not compatible with the auto import feature. This is very unlikely to be fixed.
Module Link
Project Usage
2533
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to automate the import and export of configuration files, as well as assist in creating modules that behave similarly to features export in Drupal 7.
Data Name
config_devel
OPENAI CHATBOT
OPENAI CHATBOT
