Modifying BLT config_split per environment settings

    See more
    • Updated

    Acquia Connector uses config_split to import changes to Drupal 8 configuration settings on a per-environment basis. 

    The problem is outlined in  https://github.com/acquia/blt/issues/3352 , but it is not a failure in BLT. BLT provides the tools to support config_split on a per-environment basis

     The "config_split" entity type does not exist.

     

     * To work around this, be sure that config_filter is enabled before config_split, and make sure that config_split is enabled through the configuration import process so that any per environment configuration can be imported correctly. 

     * Clear caches, including Drupal cache and Memcache to flush any database values that may be stored in cache.  Note, bootstrapping Drupal to repopulate caches with items is resource intensive and causes extra load for your database layer. Please keep this in mind when scheduling code deployments. 

    If you prefer to manage this within Drupal, consider using the Configuration Split Manager module https://www.drupal.org/project/config_split_manager which provides a user interface to help manage configuration. 

     

    Essentially, there are two approaches, use BLT to use properly configure the Config split, 

    This is some example code for local users of vagrant, that uses drush to enable config_splat and BLT to create the splits

    vagrant ssh

drush @my-project.local en config_split
drush @my-project.local cr
drush @my-project.local cex
blt splits

drush @my-project.local cim

     

    Disabling config_split

    If you are not using config_split and prefer to disable it, add the following to your blt/blt.yml file: 

    cm:
  strategy: core-only

     

    Note: do not use Config Split to manage Translation! 

    Note: We recommend the Configuration Translation module https://www.drupal.org/docs/8/core/modules/config-translation to support multiple languages.  Potion is another good tool for managing translations https://www.drupal.org/project/potion

     

    This Drupal.org issue for Acquia Connector outlines one approach to resolve this in future versions  https://www.drupal.org/project/acquia_connector/issues/2864697 

    Related articles