drupal-config-mgmt

Export, import, and manage environment-specific Drupal configurations via drush commands and config splits.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mgifford/drupal-core --skill drupal-config-mgmt-mgifford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drupal-config-mgmt
Source: https://github.com/mgifford/drupal-core/tree/main/.agents/skills/drupal-config-mgmt
Command: npx skills add https://github.com/mgifford/drupal-core --skill drupal-config-mgmt-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing Drupal configuration across multiple environments can be complex and error-prone, leading to inconsistent setups and deployment challenges.

Core Features & Use Cases

  • Config Import and Export: Facilitates seamless transfer of configuration files between local, staging, and production environments.
  • Config Splits Management: Handles environment-specific configuration changes through complete and partial splits, ensuring correct feature enablement or override per environment.
  • Use Case: A developer can export the current active configuration, modify split definitions, and deploy environment-specific settings like API keys or module toggles without disturbing the base config.

Quick Start

Use the drush commands to export current configuration, modify split files in config/{split-name}/, and import to activate environment-specific setups.

Frequently Asked Questions about drupal-config-mgmt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Drupal configuration across multiple environments?

Drupal configuration management across multiple environments is handled by exporting and importing configuration files with scripted Drush commands and config splits. This approach ensures consistent deployment workflows and segregates environment-specific overrides.

What is the best way to deploy environment-specific Drupal configuration settings?

Deploying environment-specific Drupal configuration settings is best achieved using config splits. You can modify split definitions in dedicated directories to override base configurations with environment-specific settings like API keys.

How do I use config splits to override Drupal modules in staging?

Config splits override Drupal modules by placing split configuration files in specific directories and importing them via Drush. This enables correct feature enablement or overrides per environment without disturbing the base config.

Can I use Drush to export and import Drupal configuration safely?

Drush can be used to export and import Drupal configuration safely through scripted commands. This minimizes risk during deployment and ensures configuration consistency across local, staging, and production setups.

Why does my Drupal configuration deployment fail between local and production?

Drupal configuration deployment failures between local and production often stem from inconsistent setups. Utilizing scripted Drush commands for config import and export ensures configuration safety and resolves environment segregation challenges.