Configuration Management Initiative 2.0 updates
summary
Overview of concrete CMI 2.0 changes and tradeoffs: core now supports installing from existing config (practical since 8.6), collapses to a single config directory, and adds a config storage export API plus an event-driven transform layer that lets modules massage exports/imports. Core also includes config_exclude_modules setting (8.8) to omit development modules during sync; it works but fails for heavy-weight things like system language and breaks profile hook_install workflows (standard profile excluded). Patches and contrib ports are listed for contribution.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:22Nuvole
- 1:15Session Outline
- 6:03Install from existing configuration
- 9:37Export API
- 10:53Config Storage Transformation API
- 12:50Exclude modules from config synchronisation
- 27:01Contrib solutions
- 29:32Distributions
- 33:07Multisite A word about multisite
related talks
31mLevel Up Your Drupal 8 Configuration Management
50mConfiguration management in Drupal 8 for beginners
37mExtend Configuration Management with "Config Split" and "Config Ignore" module
30mConfiguration Management Patterns
41mConfigman - the grand unified theorem of configuration
38mThe Magical Configuration Management Unicorn
28mChange management (Keep it Simple, Stupid!)
22mBreaking Changes Without Breaking Users: Lessons from Packit 1.0