Config Guardian
Config Guardian helps teams manage Drupal configuration changes with confidence by providing point-in-time snapshots, visual impact analysis, and a reliable rollback system. It allows developers and SREs to see the potential risks of configuration changes and easily revert to a previous state if something goes wrong.
Config Guardian elevates Drupal configuration management to an enterprise standard. It provides a comprehensive safety net for development teams by introducing point-in-time snapshots, advanced impact analysis, and a reliable rollback engine.
While Drupal's core CMI is powerful, it lacks historical context and granular risk assessment. Config Guardian fills this gap, allowing Site Reliability Engineers (SREs) and developers to deploy changes with absolute confidence.
🛡️ Config Guardian Core Features
- Instant Snapshots: Capture Active Config + Sync Directory in seconds.
- Safe Rollback Engine: Simulation mode and conflict detection before restoring.
- Visual Impact Analysis: D3.js interactive graph for dependency mapping.
- Risk Assessment: Automatic risk scoring (0-100) for pending changes.
- Integrity Verification: SHA-256 hashing ensures data is never corrupted.
- Audit Trails: Detailed activity logging for compliance (Who, What, When).
- Automated Backups: Hourly, Daily, or Weekly schedules with retention policies.
🚀 Why use Config Guardian?
Deploying configuration changes to production can be stressful. A missing dependency or an unexpected override can break critical site functionality. Config Guardian allows you to "Look before you leap" and "Undo" if you slip.
1. Visual Dependency Analysis
Don't read YAML files to understand relationships. Use the built-in Dependency Graph to visualize exactly how modifying a Field Storage will impact your Views, Search Indexes, and Form Displays. The module calculates a Risk Score to warn you about high-impact changes.
2. Disaster Recovery Strategy
Core configuration import is destructive. Config Guardian makes it reversible. Before any import, the system takes an automatic snapshot. If something goes wrong, the Rollback Engine restores the site to its exact previous state—including the sync directory—ensuring zero downtime.
📦 Installation
composer require drupal/config_guardian drush en config_guardian -y
🔧 Advanced Integration
- Drush Support: Full CLI integration for CI/CD pipelines (
drush cg-snap,drush cg-rollback). - Performance: Zero impact on frontend performance. Admin dashboard uses smart caching tags.
- Security: Snapshots are stored with optional GZIP compression and strict database-level access controls.
Developed and maintained by Andrés Moreno. Architecture follows strict Drupal Coding Standards and Enterprise Security Best Practices.
Depends on
Dependencies of the latest stable release
- config Drupal core
- file Drupal core
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.
Activity
Release Timeline
Releases
| Version | Type | Core | Notes | Release date | |
|---|---|---|---|---|---|
| 1.0.3 | Stable | 10–11 | Drupal 12 readiness: declares ^12 compatibility, uses DeprecationHelper for the RequirementSeverity transition in hook_requirements(), and removes two unused component templates that had a latent Twig syntax error. Safe upgrade from 1.0.2. | Jun 12, 2026 | |
| 1.0.2 | Stable | 10–11 | Critical fix: removes the leftover procedural hook wrappers that caused LogicException("should not implement <hook> more than once") on render in 1.0.1. Strongly recommended. | Jun 8, 2026 | |
| 1.0.1 | Stable | 10–11 | Maintenance and hardening release from the security advisory coverage review: adds a test suite and CI, fixes a snapshot-restore bug and a Drupal 11.2 deprecation, and improves DI, i18n and coding-standards compliance. Safe upgrade from 1.0.0. | May 25, 2026 | |
| 1.0.0 | Stable | 10–11 | Initial stable release | Dec 10, 2025 |