Automatically unpack recipes on project creation

This is probably the riskier proposition, since deployments that depend on doing a composer install at the remote end, then reapplying the recipes, will not work

Trying to think of a use-case for this workflow, but struggling a bit.

I would expect that people would apply the recipes locally, export configuration, and commit the configuration to git, then import it on production (same as config changes without recipes). Or.. if they're building a recipe-based hosted demo or similar that they'd commit the recipes themselves to git. As long as those two work, then breaking a workflow of composer install locally + recipe apply remote without either exporting config or committing to git seems fine.

Re #5: Yeah, I'm not necessarily saying it's a workflow that anyone would actually use, but I merely raise it because people have all sorts of wonky workflows and this could be a major change to some of them. I guess this is merely a call for strong documentation.

How to manually test this:

composer create-project drupal/cms:dev-recipe-unpack -s dev --repository='{"type":"vcs","url":"https://git.drupalcode.org/issue/drupal_cms-3524255.git"}' DIRNAME

Everything should install as normal, and you should be able to install Drupal CMS, but you should also see many modules added to the top-level composer.json, and few (if any) recipes.

The code in this merge request looks fine, but I think the ideal situation would be to also remove the recipes from the code base.

Like project browser can list and install projects from Drupal.org's JSON API, I feel like we should also have a browser that would list the approved Drupal CMS recipes from Drupal.org. When a user chooses to apply a recipe, the recipe is downloaded, applied, unpacked, and removed in one step.

That way, the recipe is truly ephemeral, and the user gets the latest version when they choose to browse and apply.

thejimbirch → credited pameeela → .

thejimbirch → credited tim.plunkett → .

Adding credit for discussions in slack.

Merged into 2.x and cherry-picked to 1.2.x.

Automatically closed - issue fixed for 2 weeks with no activity.