Drupal v0.1.0

Vamao Drupal Config Guard OS

Catch Drupal config drift, split mistakes, ignored live edits, and missing modules before a production deploy turns into a recovery call.

Vamao Drupal Config Guard OS is for Drupal teams that have felt the quiet panic before a production config import: the YAML looks fine, staging passed, but nobody is fully sure whether production has live Webform changes, environment-only config, inactive splits, or a module mismatch waiting to break the release.

Most Drupal config incidents are not caused by careless developers. They happen because client edits, split rules, ignored config, contrib module changes, and hosting environments move at different speeds. The deploy risk hides until drush cim starts. Config Guard OS gives the team a preflight gate before that moment.

Why it matters

A broken config import is not just a technical error. It can block editors, erase live-managed changes, delay a launch window, and force developers into emergency diff work while stakeholders wait. Config Guard OS is designed to catch those risks early enough to decide, fix, or postpone before production is touched.

What the module checks

Config Split risk: inactive or missing splits, module split pitfalls, environment-only config in the wrong directory, and suspicious split status mismatches.
Config Ignore risk: live-managed config such as Webforms, blocks, Site Studio, and environment settings that may be overwritten by the next import.
core.extension risk: modules or themes that config expects but the codebase does not provide.
Import/export drift: active config and sync config differences grouped into safe, warning, and critical categories.
CI output: machine-readable JSON for deployment pipelines and a merchant-safe report for project managers.

How teams use it

Install the licensed Drupal module in a Drupal 9, 10, or 11 project.
Connect the VamaoLabs license key and site token in Drupal admin.
Run the Drush preflight locally, on staging, or in CI before config import.
Review warnings for split status, ignored config, live-edit drift, and module mismatches.
Optionally sync redacted findings to VamaoLabs for multi-site deployment history and reporting.

After purchase

Customers get a dashboard guide with download, install, license activation, Drush, CI, and troubleshooting steps. The guide is linked from the Licenses and Downloads pages so the setup path stays visible after checkout.

Privacy by default

Hosted sync stores redacted drift fingerprints, config object names, module names, risk categories, and environment metadata. It does not upload full secrets or raw config values by default.

Features

Preflight checks before config imports touch production
Config Split and Config Ignore risk detection for Drupal 9, 10, and 11 projects
Protection report for live-edited Webforms, blocks, Site Studio, and environment-specific config
Module dependency and core.extension mismatch warnings before drush deploy fails
Redacted hosted drift snapshots for agency multi-site monitoring
CI-ready JSON output and Drush command for deployment pipelines
Post-purchase setup guide, license activation, release downloads, and site-limited paid sync

Installation Guide

Purchase a VamaoLabs license and open the product setup guide from your dashboard.
Download the module package from your Downloads page when the release package is available.
Install the module in your Composer-managed Drupal 9, 10, or 11 project and enable vamao_config_guard.
Configure the license key, site token, endpoint, environment, and protected config patterns in Drupal admin.
Run the Drush preflight before config import and optionally sync redacted findings to VamaoLabs.

Open post-purchase setup guide