Work out how to handle service injection and re-injection in \Drupal\Core\Recipe\RecipeRunner

Automatic Updates has a similar problem; it handles it by having the auto-update console command re-invoke itself, so that Drupal is booted again.

What if the recipe runner did something similar? If you ran the command drupal recipe path/to/recipe, it could actually do something like this under the hood:

drupal recipe:prerequisites path/to/recipe
drupal recipe:extensions path/to/recipe
drupal recipe:configuration path/to/recipe
drupal recipe:content path/to/recipe

Each invocation would boot Drupal anew.

@phenaproxima it's not that simple though - changing config can rebuild the container... let alone each module install inside the recipe.

moved to Drupal Core