- 🇺🇸United States freelock Seattle
FWIW, Reroute Email uses this pattern, as do a bunch of commerce module -- a global "enable" config that can act as a kill switch. It's a really handy pattern.
Config Split introduces a ton of complexity and confusion to managing configuration -- which means opportunities to make mistakes. We highly prefer a global config with specific environment overrides -- this allows us to have sane settings in the database for all dev environments, and hard-code specific overrides for production in a production-specific environment file.
Even better is being able to set these with environment variables, but that's an entirely different topic...
- 🇳🇿New Zealand davidwhthomas
As noted in an earlier comment, adding this to settings.php in recent drupal / drush versions, prevents exporting the related config from dev.
// @see https://www.drupal.org/node/3079028 $settings['config_exclude_modules'] = ['stage_file_proxy'];For example, it will prevent exporting
stage_file_proxy.settings.yml core.extension.yml (with stage_file_proxy)