[meta] Config validation for a more reliable Drupal + reliable Recipes from the start

Created on 13 March 2024, 9 months ago

Updated 24 June 2024, 6 months ago

Numerous bugs are caused by code expecting config to contain certain key-value pairs and expect those values to be a certain shape, but they aren't
👆 This often leads to broken update paths!
Very often working on core is slowed down by invalid configuration in an existing test or new tests.
Sites using configuration management often have to deal with hard-to-understand config diffs, and worse, when using modules like https://www.drupal.org/project/config_split → , chances are that the resulting config is invalid.
Recipes → will install modules/themes, apply other recipes, but will primarily be installing and updating configuration. Combining many recipes == combining lots of config. This results in a Cambrian explosion of config, and will make it very probable that a combination of recipes results in a broken ("misconfigured") site. UNLESS we make config validatable, and validate config after applying a recipe: #3405328: [meta] Make recipes safer to use in the real world by supporting config validation and rolling back a broken recipe →
We'd like to be able to enable new use cases for Drupal, such as decoupled admin UIs, but that requires the ability to safely modify configuration via APIs, and hence needs thoroughly validatable config. That would unblock ✨ [PP-2] POST/PATCH config entities via REST for config entity types that support validation Needs work .