Problem/Motivation

Installations using the minimal install profile do not have immediate/out of the box ability to import/export configuration. This is particularly problematic when using a workflow where you need to install Drupal and immediately revert to an exported config, e.g. when using drush site-install minimal --config-dir /sync. See this issue on Drush for some further exploration and background.

Proposed resolution

Include config module in the list of dependencies for the minimal install profile.

Remaining tasks

  1. Review by community regarding efficacy of approach. We don't need to change core to make a Drush command work, for instance, but configuration import/export is a common "expert" feature that is a strong candidate for inclusion in a profile aimed at that user group.
  2. If accepted, a change record.

User interface changes

None.

API changes

No API changes.

Data model changes

None.

(Marking this as "other" per alexpott's feedback about components here)

CommentFileSizeAuthor
config-minimal-profile.patch326 bytesbradjones1

Comments

bradjones1 created an issue. See original summary.

bradjones1’s picture

bradjones1
Primary language English
commented
Related issues: +#1370708: Remove Node module from Minimal installation profile, +#2658864: Do not require dblog as part of the minimal install profile, +#1946526: Clean up Minimal profile modules, +#1664894: Clarify Minimal profile's use-case and description
bradjones1’s picture

bradjones1
Primary language English
commented
Status: Active » Needs review
bradjones1’s picture

bradjones1
Primary language English
commented

I should note the Drush issue I linked above has been resolved to work without this module installed, however I'll keep this up since I think it's still a good question whether this should be included in minimal.

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented

Maybe drush should enable that module before doing the action? Then we don't need to add a module to minimal that may not be needed for everybody?

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented

Maybe drush should enable that module before doing the action? Then we don't need to add a module to minimal that may not be needed for everybody?

I think this is the best option.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Closed (outdated)

This dependency in Drush was narrowed/removed in May 2016.