Config Split and Config Ignore Checklist for Drupal Agencies

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.