Configuration system data types

There are multiple places configuration data may be found:

  1. Module-provided defaults: Any module may provide default configurations in its config/install directory. These configurations are imported to the active configuration upon installation. A module may provide either:

    • Configuration in its own namespace (e.g., its default settings and configurations for its own functionality).
    • Configuration in another module's namespace (e.g., a default view of nodes provided by node.module).
  2. Active configuration: The active configuration is the location of the current, canonical configuration for a given site. This includes both settings and stored ConfigEntity objects like views.

  3. Staging: The configuration staging directory is used for deploying new configurations on a site. Configuration files in this directory are compared to the active configuration and imported or synchronized.

  4. (Proposed) Snapshots: See #1515312: Add snapshots of last loaded config for tracking whether config has changed. The proposed snapshot directory creates a config snapshot following a successful import.

Views functionality

There are a number of operations users might wish to perform on a view:

  1. Add a new view:
    • Through the UI.
    • From a module default.
    • From imported/staged configuration.
  2. Update an existing view:
    • Through the UI.
    • From a version update to an already-installed module.
    • From imported/staged configuration.
  3. Enable or disable an existing view:
    • During module installation or update.
    • Through the UI.
    • As part of a staging operation.
  4. Revert an existing view:
    • To the state provided in a module default.
    • To the saved state before recent changes when editing in the UI.
    • To an earlier revision.
    • As part of the synchronization workflow.
  5. List all views, their metadata, their original source/owner, and their active status.
  6. Stage and manage changes or updates through the UI.
  7. Locate and/or download a copy of the active configuration through the UI
    • For staging on restrictive hosting environments or in certain staging workflows.
    • For debugging or troubleshooting.

Relevant issues

Comments

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

.

xjm’s picture

Issue summary: View changes

.

xjm’s picture

Issue summary: View changes

Updated issue summary.

tim.plunkett’s picture

Priority: Normal » Major
tim.plunkett’s picture

Issue summary: View changes

added another issue

andypost’s picture

Not sure which issue more suitable but ConfigEntity needs implemet ::loadByProperties for its controller

andypost’s picture

Issue summary: View changes

.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

heyrocker’s picture

Priority: Major » Normal

Demoting to normal per discussion with xjm and timplunkett

heyrocker’s picture

Issue summary: View changes

Updated issue summary.

tim.plunkett’s picture

Issue summary: View changes

Removed dupe #1790398

xjm’s picture

Issue summary: View changes

rearrange

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Removing myself from the author field so I can unfollow. --xjm

xjm’s picture

Issue summary: View changes
alexpott’s picture

Issue summary: View changes

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.