Modules such as Config Split want to modify the configuration when it is synchronized between the database and the exported yaml files. This module provides the API to do so but does not influence a sites operation.
Unlike Config Filter 1.x which swaps the config.storage.sync service from Drupal 8 core,
Config Filter 2.x applies the filters when the new Drupal core config storage transformation api is used.
This means that modules that previously used Config Filter now work with the new api.
Modules depending on Config Filter can depend on both 1.x or 2.x as the Config Filter API is the same.
A ConfigFilter is a plugin. This module provides the plugin definition, the plugin manager and the storage factory. A ConfigFilter can have the following annotation:
/**
* @ConfigFilter(
* id = "may_plugin_id",
* label = @Translation("An example configuration filter"),
* weight = 0,
* status = TRUE,
* storages = {"config.storage.sync"},
* )
*/See \Drupal\config_filter\Annotation\ConfigFilter.
The weight allows the filters to be sorted. The status allows the filter to be
active or inactive, the ConfigFilterManagerInterface::getFiltersForStorages
will only take active filters into consideration. The weight, status and
storages are optional and the above values are the default.
Plugins are only available from enabled modules. If you want to provide a
config filter from a php library, all you have to do is implement the
\Drupal\config_filter\ConfigFilterManagerInterface and add it to the
service container with a config.filter tag.
Services with higher priority will have their filters added first.