drupal-config-management

Automate Drupal configuration management across dev, staging, and production environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuration in Drupal is declarative and lives in YAML, but coordinating config across development, staging, and production is error-prone. This skill documents patterns for managing multi-environment configuration, including config_split, config_ignore, and the standard directory hierarchy (config/sync, config/install, and optional directories) to ensure reliable deployments.

Core Features & Use Cases

  • Environment-specific configuration: Use config_split to apply environment overrides while preserving a shared base configuration.
  • Controlled import/export workflows: Align with Drush cex/cim processes for safe and predictable deployments.
  • Managed install vs optional config: Distinguish install-time config from optional overrides to satisfy dependencies and deployment goals.

Quick Start

Set up config_split and config_ignore patterns and organize config directories (config/sync, config/install, and optional) to enable reliable multi-environment deployments.

Frequently Asked Questions about drupal-config-management

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 across multiple environments is managed by exporting YAML files to a standard directory layout and synchronizing them using Drush cim and cex workflows. This ensures reliable dev, staging, and production deployments.

What is the best way to set up config_split for environment-specific Drupal config?

Config_split for environment-specific Drupal config is set up by organizing a shared base configuration and applying environment overrides through standard directories like config/sync. This preserves shared settings while allowing targeted deviations.

How do I use Drush cim and cex for safe Drupal config deployments?

Drush cim and cex are used for safe Drupal config deployments by exporting configuration changes to YAML and importing them across environments. This controlled workflow ensures predictable and error-free synchronization.

When should I use config/install versus optional directories in Drupal?

Config/install directories in Drupal should be used for required install-time configuration, while optional directories handle overrides that depend on certain conditions or dependencies being met during deployment.

Does Drupal config management work with config_ignore to exclude specific settings?

Drupal config management works with config_ignore to exclude specific environment settings from being overwritten during synchronization. This pattern prevents local configurations from being exported and deployed incorrectly.