Recipe Ops

Recipe Ops adds the workflow Drupal recipes are missing: a plan before you apply, a checkpoint while you apply, and a revert afterwards.

Drupal recipes are "apply once and forget". There is no preview of what a recipe will change and no way to undo it once applied (see #3333076: Support reverting a recipe). Recipe Ops wraps core's Recipe API with a small set of Drush 13 commands and an audit report.

Commands

• drush recipe-ops:plan RECIPE — lists the modules, themes, configuration, config actions, content and inputs a recipe and its dependencies would touch. Changes nothing. --format=json for CI and review.
• drush recipe-ops:apply RECIPE — shows the plan, asks for confirmation, takes a core configuration checkpoint, applies the recipe, and records exactly what was installed and created. A recipe that throws part-way is rolled back automatically.
• drush recipe-ops:revert ID — previews the exact configuration changes and content deletions, then deletes the content the recipe created and restores the checkpoint through the standard configuration importer, which also uninstalls the modules the recipe installed.
• drush recipe-ops:list and drush recipe-ops:show ID — history of every application, also available at Reports → Recipe applications.

Safety model

Core configuration checkpoints form a linear history: restoring an older checkpoint also undoes everything applied after it. Recipe Ops therefore refuses to revert an application while newer ones are still in effect unless you pass --cascade, which reverts them newest-first, and it always prints the full list of configuration objects and content entities that will change before asking for confirmation.

Requirements

• Drupal 11.1 or later
• Drush 13 for the commands (the module installs without Drush, but the workflow is command-line first)

Stability

Recipe Ops builds on core's Recipe and checkpoint APIs, which core still marks as experimental. The module pins drupal/core: ^11.1 and runs its test suite (unit, kernel and functional) against the next major release in GitLab CI so breaking changes surface early. Feedback and use cases from people maintaining site templates are especially welcome in the issue queue.