Roadmap for CMI 2

Created on 24 October 2018, about 6 years ago

Updated 24 May 2023, over 1 year ago

In #2957423: Proposal: Configuration Management 2.0 initiative → we collected a broad outline of pain points and areas in which Drupal's configuration management can be improved.
In this issue we curate the road map for the efforts.

The target version of Drupal may change as time moves on depending on the progress of the relevant issues.

Documentation improvements with clear recommendations for common setups for different requirements.

🐛 Allow an install hook in profiles installing from configuration Needs work allow profiles to have install hooks and work with config install.

🌱 Plan

Status

Active

Component

Miscellaneous

Created by

🇨🇭Switzerland bircher 🇨🇿

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇺🇸United States effulgentsia
Hi. Am I correct in understanding that as of right now, even if you're installing a new site from a config_sync directory that the config in that directory is still required to have a site UUID in it? And so you can't install two different new sites, for which you want the exact same starting configuration, other than wanting them to have two different site UUIDs, from the same config_sync directory, without injecting something else (like a Drush command to change the site UUID) into the process?

If so, is addressing that part of the CMI 2 roadmap? If so, is there an open issue for that specifically? Thanks!
Comment over 1 year ago →
🇺🇸United States effulgentsia
Re #14, I created https://www.drupal.org/project/config_sync_without_site_uuid → . Feedback welcome in that issue queue as to if or why that project is a bad idea :)

Production build 0.71.5 2024