Fixed Config

The Fixed Config module provides a way for other modules to define configuration that is permanently defined in module code.

Features

Fixed config cannot be changed or deleted. If a new version of a module providing a fixed config has changes, the configuration item in the site will update accordingly.

For example, a commerce module could provide a view of the user's shopping cart. Defining this as fixed config ensures that site admins can't make changes that would break the functionality of the view, and that updates in the commerce module are reflected in the view installed in the site. The commerce module can still allow customisation of the view by providing a setting where the admin selects which view is used for the shopping cart, but the default view remains usable and the commerce module can easily make changes to it.

(This is the same concept as how back in Drupal 7, some modules provided hooks to define default items, such as hook_views_default_views().)

Fixed config can be static or derived:

• Static fixed config is just a single piece of configuration.
• Derived fixed config is derived automatically from admin-created config. For example, a vocabulary that is created for each node type. When the dependee config, the node type, is created by an admin, a dependent fixed config the vocabulary is automatically created by the Fixed Config module.

Recommended modules/libraries

The Configuration development module can be used to help with creation of fixed configuration.