Label for the Configuration Split setting.
A unique machine-readable name. Can only contain lowercase letters, numbers, and underscores.
Static Settings
Describe this config split setting. The text will be displayed on the Configuration Split setting list page.
Storage
Select where you would like the split to be stored.
Folder: A specified directory on its own. Select this option if you want to decide the placement of your configuration directories.
Collection: A collection inside of the sync storage. Select this option if you want splits to be part of the main config, including in zip archives.
Database: A dedicated table in the database. Select this option if the split should not be shared (it will be included in database dumps).
The directory, relative to the Drupal root, in which to save the filtered config. This is typically a sibling directory of what you defined as $settings["config_sync_directory"] in settings.php, for more information consult the README.
Configuration related to the "filtered" items below will be split from the main configuration and exported to this folder.
The weight to order the splits.
Status
Active splits get used to split and merge when importing and exporting config, this property is likely what you want to override in settings.php, for example: $config["config_split.config_split.example"]["status"] = FALSE;
This setting will override the status of the split with a config override saved in the database (state). The config override from settings.php will override this and take precedence.
Changing the status does not affect the other active config. You need to activate or deactivate the split for that.
These settings can be overridden in settings.php
Complete Split
Modules
Select modules to split. Configuration depending on the modules is changed as if the module would be uninstalled or automatically split off completely as well.
Configuration items
Select configuration to split. Configuration depending on split modules does not need to be selected here specifically.
Select additional configuration to split. One configuration key per line. You can use wildcards.
Complete Split: Configuration listed here will be removed from the sync directory and saved in the split storage instead. Modules will be removed from core.extension when exporting (and added back when importing with the split enabled.). Config dependencies are updated and their changes are recorded in a config patch saved in in the split storage.
Partial Split
Configuration items
Select configuration to split partially.
Select additional configuration to partially split. One configuration key per line. You can use wildcards.
Partial Split: Configuration listed here will be left untouched in the main sync directory. The currently active version will be compared to the config in the sync directory and what is different is saved to the split storage as a config patch.
Use this for configuration that is different on your site but which should also remain in the main sync directory.
Advanced settings
By default, splits are independent, but with this setting a split can become "stackable". This means that when completely splitting config, the data written to the split storage can be modified by splits with a lower weight. During the partial split the config is compared to the sync storage with all higher weight splits merged into it.
Use this if you are "extending" splits you create first. This has a performance impact.
By default, dependents will be patched, by checking this option, splits will behave as they did in 1.x in which all dependencies will also fully split.
Moves focus to sticky header actions