Recently, I decided to revisit the topic of Drupal configuration management, with a special focus on the Config Split module. Configuration management, first introduced in Drupal 8, was a fantastic addition to the platform and has paved the way for major improvements in CI/CD workflows over the years.
When combined with the Config Split module, Drupal’s configuration system becomes even more powerful—allowing developers to tailor configuration based on environment or feature, depending on their preferred implementation strategy.
To revisit this topic, I initially planned to write a blog post as an updated version of my Drupal GovCon training from 2021. Then, Mike Anello launched a new YouTube series called DrupalEasy Show & Tell and invited suggestions for topics to cover. That gave me an even better opportunity to share my enthusiasm for Config Management and Config Split—through this excellent video series!
I hope you enjoyed the video! Before wrapping up, I wanted to share a few additional notes.
Here are a couple of add-on modules (also featured in my training) that I recommend exploring:
- Configuration Read-Only – This module lets you lock down configuration changes on production environments and display a notice to users attempting to edit configuration. It’s a great way to alert users and prevent accidental configuration changes that could impact the site.
- Config Ignore – This module allows you to specify configuration items that should be ignored during import. It’s especially useful when certain configuration needs to be edited directly on production but shouldn’t be overwritten on the next deployment.
Hopefully, after reading (and watching!) this, you have a renewed appreciation for the power of configuration management in Drupal and are excited to explore all the possibilities it offers. I love working with Config Management and Config Split, and I hope you will too!
