Suggested commit message
git commit -m 'Issue #2487592 by Schnitzel, alexpott, cilefen, joshi.rohit100: CMI: don'\''t ship with a default "active" directory that is empty in most Drupal installations'
We used to have an active CMI config directory which actually contained configuration, but with
But still we ship with an active directory, which is empty all the time, unless you install a contrib module like https://www.drupal.org/project/config_devel that saves the configuration again in a directory.
But not a lot of Sites will have that installed.
And also I've seen a lot of developers being confused about an empty active configuration directory and wondering that something is broken or so.
Don't create an active directory per default, let contrib modules that need that work via the requirements system to tell the users that they should create a new config directory
- Agree (done)
- Write Patch (done)
User interface changes
Beta phase evaluation
|Issue category||Task because it is not an actual programming Bug. More a DX Bug. We create an active directory but never use it by default, which can be confusing and misleading for Developers. Actually this already happened to Amazee Labs and our environments.|
|Issue priority||Major because CMI is a new system that nobody really knows yet, the less confusion be bring with it, the better.|
|Disruption||This will break some contrib modules that expect an active config, like config_devel or drush. But both maintainers of these contrib modules already agreed to the change and will update their modules.|
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 110,674 pass(es). View
FAILED: [[SimpleTest]]: [PHP 5.5 MySQL] Unable to apply patch cmi_don_t_ship_with_a-2487592-37.patch. Unable to apply patch. See the log in the details link for more information. View
FAILED: [[SimpleTest]]: [PHP 5.5 MySQL] 104,174 pass(es), 2 fail(s), and 0 exception(s). View