Problem/Motivation

It should be possible for install profiles just to be a full site export of configuration. However in order to do this you need to remove the core.extension.yml file and move this information into the profile's .info.yml.

Proposed resolution

If the profile has a core.extension.yml file use this information to populate the dependencies and theme information.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

alexpott created an issue. See original summary.

alexpott’s picture

This is related to the www.drupal.org/project/config_installer project. One advantage that has is that it using the ConfigImporter class which resolves dependencies already. Maybe if that functionality is moved into core profiles could have a flag that just says use the ConfigImporter for install rather than the installer...

alexpott’s picture

Given issues like #2672340: user_user_role_insert should not exist install profiles containing a full export of config without having www.drupal.org/project/config_installer in core might be too hard to do.

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

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now 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.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.