Loading core/assets/scaffold/files/example.settings.local.php +24 −0 Original line number Diff line number Diff line Loading @@ -129,3 +129,27 @@ * directory. */ $settings['skip_permissions_hardening'] = TRUE; /** * Exclude modules from configuration synchronisation. * * On config export sync, no config or dependent config of any excluded module * is exported. On config import sync, any config of any installed excluded * module is ignored. In the exported configuration, it will be as if the * excluded module had never been installed. When syncing configuration, if an * excluded module is already installed, it will not be uninstalled by the * configuration synchronisation, and dependent configuration will remain * intact. This affects only configuration synchronisation; single import and * export of configuration are not affected. * * Drupal does not validate or sanity check the list of excluded modules. For * instance, it is your own responsibility to never exclude required modules, * because it would mean that the exported configuration can not be imported * anymore. * * This is an advanced feature and using it means opting out of some of the * guarantees the configuration synchronisation provides. It is not recommended * to use this feature with modules that affect Drupal in a major way such as * the language or field module. */ # $settings['config_exclude_modules'] = ['devel', 'stage_file_proxy']; core/core.services.yml +5 −0 Original line number Diff line number Diff line Loading @@ -1280,6 +1280,11 @@ services: tags: - { name: event_subscriber } arguments: ['@config.manager', '@config.storage', '@config.storage.snapshot'] config_exclude_modules_subscriber: class: Drupal\Core\EventSubscriber\ExcludedModulesEventSubscriber arguments: ['@config.storage', '@settings', '@config.manager'] tags: - { name: event_subscriber } exception.needs_installer: class: Drupal\Core\EventSubscriber\ExceptionDetectNeedsInstallSubscriber arguments: ['@database'] Loading core/modules/config_environment/src/EventSubscriber/ExcludedModulesEventSubscriber.php→core/lib/Drupal/Core/EventSubscriber/ExcludedModulesEventSubscriber.php +1 −1 Original line number Diff line number Diff line <?php namespace Drupal\config_environment\EventSubscriber; namespace Drupal\Core\EventSubscriber; use Drupal\Core\Config\ConfigManagerInterface; use Drupal\Core\Config\StorageInterface; Loading core/modules/config_environment/tests/config_exclude_test/config/install/system.menu.exclude_test.yml→core/modules/config/tests/config_exclude_test/config/install/system.menu.exclude_test.yml +0 −0 File moved. View file core/modules/config_environment/tests/config_exclude_test/config/install/system.menu.indirect_exclude_test.yml→core/modules/config/tests/config_exclude_test/config/install/system.menu.indirect_exclude_test.yml +0 −0 File moved. View file Loading
core/assets/scaffold/files/example.settings.local.php +24 −0 Original line number Diff line number Diff line Loading @@ -129,3 +129,27 @@ * directory. */ $settings['skip_permissions_hardening'] = TRUE; /** * Exclude modules from configuration synchronisation. * * On config export sync, no config or dependent config of any excluded module * is exported. On config import sync, any config of any installed excluded * module is ignored. In the exported configuration, it will be as if the * excluded module had never been installed. When syncing configuration, if an * excluded module is already installed, it will not be uninstalled by the * configuration synchronisation, and dependent configuration will remain * intact. This affects only configuration synchronisation; single import and * export of configuration are not affected. * * Drupal does not validate or sanity check the list of excluded modules. For * instance, it is your own responsibility to never exclude required modules, * because it would mean that the exported configuration can not be imported * anymore. * * This is an advanced feature and using it means opting out of some of the * guarantees the configuration synchronisation provides. It is not recommended * to use this feature with modules that affect Drupal in a major way such as * the language or field module. */ # $settings['config_exclude_modules'] = ['devel', 'stage_file_proxy'];
core/core.services.yml +5 −0 Original line number Diff line number Diff line Loading @@ -1280,6 +1280,11 @@ services: tags: - { name: event_subscriber } arguments: ['@config.manager', '@config.storage', '@config.storage.snapshot'] config_exclude_modules_subscriber: class: Drupal\Core\EventSubscriber\ExcludedModulesEventSubscriber arguments: ['@config.storage', '@settings', '@config.manager'] tags: - { name: event_subscriber } exception.needs_installer: class: Drupal\Core\EventSubscriber\ExceptionDetectNeedsInstallSubscriber arguments: ['@database'] Loading
core/modules/config_environment/src/EventSubscriber/ExcludedModulesEventSubscriber.php→core/lib/Drupal/Core/EventSubscriber/ExcludedModulesEventSubscriber.php +1 −1 Original line number Diff line number Diff line <?php namespace Drupal\config_environment\EventSubscriber; namespace Drupal\Core\EventSubscriber; use Drupal\Core\Config\ConfigManagerInterface; use Drupal\Core\Config\StorageInterface; Loading
core/modules/config_environment/tests/config_exclude_test/config/install/system.menu.exclude_test.yml→core/modules/config/tests/config_exclude_test/config/install/system.menu.exclude_test.yml +0 −0 File moved. View file
core/modules/config_environment/tests/config_exclude_test/config/install/system.menu.indirect_exclude_test.yml→core/modules/config/tests/config_exclude_test/config/install/system.menu.indirect_exclude_test.yml +0 −0 File moved. View file