Drupal Deployment Ops June 23, 2026 158 views

Config Split and Config Ignore Checklist for Drupal Agencies

A client-site checklist for multi-environment Drupal deployments.

Drupal agencies often manage many sites where production content editors, staging releases, and local development all touch configuration differently. Config Split and Config Ignore can keep this sane, but only when the rules are visible before every release.

Agency release checklist

  • Confirm which split should be active for the target environment.
  • Confirm Webform, block, and environment config that clients edit live is protected.
  • Check that ignored config is actually covered by the project's ignore rules.
  • Verify contrib modules expected by config exist in the deployed codebase.
  • Review staging differences separately from production differences.
  • Attach the preflight output to the release ticket before approving deployment.

Where Config Guard OS fits

Vamao Drupal Config Guard OS gives agencies one repeatable preflight process for Drupal 9, 10, and 11 projects. The local report helps the developer catch technical risk. The hosted redacted sync helps the account or release manager see which client sites have recurring config drift before it becomes an emergency.

## Add a deploy-blocker decision table | Signal | Review | Block when | |---|---|---| | Expected Config Split | Confirm its machine name exists in active configuration. | The expected split is missing. | | Config Ignore policy | Confirm live-edited Webforms, blocks, and environment objects match protected patterns. | A protected object would change or no policy exists. | | `core.extension` | Compare expected modules and themes with deployed code. | Config expects an extension absent from the release. | | Active versus sync drift | Classify differences for the target environment. | A critical difference cannot be explained. | ### Agency rollout Start on staging, save the policy, reopen it, and attach JSON output to the release ticket. Expand only after every critical finding is reviewed. Config Guard supports this process but does not replace backups, approval, or exact-artifact browser qualification. Link readers to the product and `/docs/vamao-drupal-config-guard-os` for installation, limits, security, and troubleshooting.

Discussion

Comments

0 approved
No approved comments yet.

Leave a comment

Comments are reviewed before they appear publicly.

Guest verification lasts 30 days for the same browser and email.

Related Posts