Last updated March 6, 2013. Created by dagmar on December 7, 2012.
Edited by jedihe. Log in to edit this page.

The configuration management module enables the ability to keep track of specific configurations on a Drupal site, provides the ability to move these configurations between different environments (local, dev, qa, prod), and also move configurations between completely different sites (migrate configurations) without the use of modules with all configuration being owned by the site.

For the most part this module provides the same functionality as a subset of the Features module. Features module is currently the go to tool for moving configuration from environment to environment and site to site, and it does a great job doing this, but "configuration management" was never really what features was intended to do. The goal of features module was to group configurations together to satisfy a certain use-case. Instead most people use features to export configuration to code to ease deployment between environments. Many of us have experienced the shortcomings of using features module for configuration management and found cases where it doesn't quite work to easily manage configuration. A couple other modules have spawned off to help with some of these shortcomings: Features Override, Features Plumber, Features Tools.

Configuration Management module takes some concepts from the Drupal 8 core configuration management initiative, specifically the concept of the activestore and datastore architecture. Read up on how Drupal 8 will manage configurations to get an idea of how this module manages configuration between the activestore and datastore.

The module knows what configuration was changed and allows users to either activate a configuration that was changed in the datastore, or write to datastore if a configuration was changed in the activestore. If you enable the Diff module, you can then see a comparison between the contents of the activestore vs. datastore.

The granularity level goes down to each specific config, rather than an entire group of them (as a feature module does). This makes it easier to activate or write to file specific configurations, without having to features-update or features-revert an entire group of configurations.

Looking for support? Visit the forums, or join #drupal-support in IRC.