Config Split Recipe

Introduction

Recipe for installing and configuring config_split into stackable client environments.

Installation

This recipe requires some manual intervention to install given the greedy matching nature of how config_split is being configured in the client_core split.

1. Require the recipe: composer require --dev discoverygarden/config_split_recipe:^1
2. Apply the recipe: php core/scripts/drupal recipe /path/to/the/recipe
3. Unpack the recipe. composer unpack discoverygarden/config_split_recipe
4. Override the state to disable the client_core split. drush csso client_core inactive
5. Ensure all other splits have stackable set to true
6. Export the configuration. drush cex
7. Remove the state override. drush csso client_core active

Troubleshooting/Issues

The apply recipe command will need to be run from Drupal's web root, for ddev environments this will be /var/www/html/web.

If you notice that you are duplicating config from another active config split in client_core when exporting config:

• Ensure that 'Stackable' is set to true for each split (such as dev, stage, prod, etc.)
  • GUI path is found at /admin/config/development/configuration/config-split/<insert split id here>/edit
  • Drush command would be something like drush config:set config_split.config_split.<insert split id here> stackable true
  • If you only noticed this problem after activating multiple splits and making other changes, you might need to just edit the config yaml directly in config/sync/config_split.config_split.*.yml and then import that with drush cim instead of making the changes in active config and exporting because these changes could get exported to a split partial; splits modifying other splits could get messy.

Having problems or solved one? contact discoverygarden.

Maintainers/Sponsors

Current maintainers:

• discoverygarden

Development

If you would like to contribute to this module create an issue, pull request and or contact discoverygarden.

License

GPLv3