Problem/Motivation

There are some configuration values that are coupled to other things in the system in such a way that overriding them would put Drupal into a nonsensical state. For example:

  • overriding core.extension without actually installing/uninstalling the modules
  • overriding values within field.storage.* that require changes to database schema to implement

Proposed resolution

  1. Option 1: do nothing other than document this in default.settings.php (see #2392319-69: Config objects (but not config entities) should by default be immutable) and hope that modules that implement overrides steer clear as well.
  2. Option 2: add an event that allows subscribers to check the state of overrides and throw an exception if something is overridden that that subscriber doesn't find acceptable.
  3. Option 3: other ideas?

User interface changes

None

API changes

?

Comments

effulgentsia’s picture

Issue summary: View changes
dawehner’s picture

Note: http://cgit.drupalcode.org/mongodb/tree/drivers/mongodb/Install/Tasks.ph... overrides existing modules. There seems also to be quite some usecases for that.

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.