Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Follow-up to: #1934700: Automated cron runs should only be enabled by default for Standard profile
Problem
- An installation profile that only wants to override a particular setting from a default module config file needs to override the entire file.
- Otherwise, all other settings are missing.
Goal
- Allow installation profiles to only override what they need to override.
Proposed solution
- Change the process of installing default configuration files for installation profiles to merge each config file with the module-provided default config file (if any), i.e.:
modules/system/config/system.cron.yml + profiles/standard/config/system.cron.yml = config/active/system.cron.yml
Comments
Comment #1
sunComment #2
markpavlitski CreditAttribution: markpavlitski commented@sun Please see #1986090: Profile config does not overwrite module default config on install (system.cron.yml) for a crossover issue, and potential fix.
Comment #3
mtiftWhile this is a the earlier issue, #1986090: Profile config does not overwrite module default config on install (system.cron.yml) has a patch
Comment #4
Dave ReidThis isn't really a duplicate, while #1986090: Profile config does not overwrite module default config on install (system.cron.yml) has landed, it still doesn't support an install profile wanting to provide only partially overridden config files, right now we still have to provide the whole config file or nothing at all. When we're providing contributed module configs, we have to be very careful to keep them in sync. For example, the Webform module config is extra long and detailed and easy to miss something has changed.
Comment #9
nedjoPer the distributions and recipes initiative, config actions are proposed to meet this need. See #3284025: Add configuration actions API and follow-up issues.