Web UI
Drush

Introduction

Ever experienced that your site's configuration was overridden by the configuration on the filesystem, when doing a drush cim?

Not anymore!

This module is a tool to let you keep the configuration you want, in place.

Lets say that you do would like the system.site configuration (which contains that sites name, slogan, email, etc) to remain untouched, on your live site, no matter what the configuration, in the export folder says.

Or maybe you are getting tired of having the devel.settings changed every time you import configuration?

Then this module is what you are looking for.

How it works

The module "hooks" in to the config import process at the very beginning and at the very end. And, honestly, it doesn't actually ignore any configuration either. It just reverts it to what it was before you initiated the import (or synchronisation).

This module will not interfere with exported configuration.

A little longer explanation

At the start, the module records what changes that are about to take place. If any of the changes touches the configuration that you have marked as ignored, in the module configuration, the current configuration is fetched and saved for later use.

At the end of the import process, the configuration saved from earlier on, is now re-inserted, and will look as it did before the configuration import.

Requirements

This module needs the config module, from D8 Core, but that's it.

Installation

Consult https://www.drupal.org/docs/8/extending-drupal-8/installing-contributed-...
to see how to install and manage modules in Drupal 8.

Configuration

Go to admin/config/development/configuration/ignore to set what configuration you want to ignore upon import.

From version 1.2 it is possible to use use wildcards, meaning that you can use system.* to ignore all config entities which name starts with system.

Limitations

For now, this module only supports changes/updates to existing configuration. Configuration marked for deletion or creation will still be deleted or created.

This module does not support changes in the core.extension yet, but I happily discus how this could be achieved, in the issue queue.

Maintainers

Current maintainers:

Supporting organizations: 
Paid for development

Project Information

Downloads