On this page
Exclude development modules from configuration synchronisation
Last updated on
11 March 2021
This documentation needs work. See "Help improve this page" in the sidebar.
This page is still work in progress and the functionality is provided by a pending core patch.
Motivation
Some modules will be installed on development machines that should not be deployed. Manually Un-installing the module before exporting the configuration and re-installing it after a configuration import is error prone. In order to avoid accidentialy exporting a modules configuration there is a setting one can set.
See the change notice.
Help improve this page
Page status: Needs work
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion