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

  1. 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

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Title: Allow installation profiles to override partial module settings » Allow installation profiles to partially override module default configuration settings
markpavlitski’s picture

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.

mtift’s picture

mtift
he/him
Primary language English
Location Minnesota, USA
CreditAttribution: mtift commented
Status: Active » Closed (duplicate)

While this is a the earlier issue, #1986090: Profile config does not overwrite module default config on install (system.cron.yml) has a patch

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid as a volunteer and at Lullabot commented
Issue summary: View changes
Status: Closed (duplicate) » Active

This 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.

Version: 8.0.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

Per the distributions and recipes initiative, config actions are proposed to meet this need. See #3284025: Add configuration actions API and follow-up issues.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.