Problem/Motivation

Reviewing a related docs https://git.drupalcode.org/project/distributions_recipes/-/blob/1.0.x/do.... I have found at least one edit to match the project roadmap. There may be others.

Steps to reproduce

Proposed resolution

  • Done - remove "Deploying the content created by a Drupal recipe is out-of-scope." which conflicts with the project Roadmap.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork distributions_recipes-3365668

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

bsnodgrass created an issue. See original summary.

bsnodgrass’s picture

bsnodgrass commented
Title: Edit to » Edit to recipe.md
bsnodgrass’s picture

bsnodgrass commented
Project: Drupal core » Recipes Initiative
Version: 10.1.x-dev » 1.0.x-dev
Component: documentation » Code

bsnodgrass opened merge request !49

bsnodgrass’s picture

bsnodgrass commented
Issue summary: View changes
Status: Active » Needs review
sonfd’s picture

sonfd
he/they
Location Portland, ME
commented

@bsnodgrass - We talked yesterday and I was in agreement with you here, that we should remove this line. However, I am reviewing this now and I think deleting this line may not be the correct action. I think this is attempting to clarify that creating content is in scope for recipes (the content will only be created in the database on the environment the recipe is applied to), but recipes are not responsible for deploying that created content to a secondary environment and/or recreating the content on those other environments.

In other words, in a standard workflow, you may apply a recipe on your local environment, test changes, export configuration and deploy to dev, stage, live, etc. Recipes will create content on the local environment, however when you deploy changes to those additional environments, e.g. dev, stage, live, etc, Recipes will not create that content on those additional environments.

thejimbirch’s picture

thejimbirch commented

If that is the case, and content creation is a requirement of recipes; then the recipe would have to be re-run on each environment.

bsnodgrass’s picture

bsnodgrass commented

While I do think it would be helpful to have content created as part of a recipe deployment, the Roadmap specifically states this in not within scope.

Do we want creation or updating of content specific to a recipe? If so we should update the Roadmap and close this issue was "won't fix"

Since the parent issue is still active, it seems this one should be postponed until that decision is finalized. I think we should leave the debate and how to address default content on the parent issue.

bsnodgrass’s picture

bsnodgrass commented
Status: Needs review » Postponed
thejimbirch’s picture

thejimbirch commented

Content is content, and while there are ways to deploy content, there is nothing in core, or being proposed in recipes that would deploy content.

If the content a recipe is providing is needed on a different environment, the recipe would need to run on that environment.

Maybe we could update the doc to include the above to add additional clarification.

thejimbirch’s picture

thejimbirch commented
Status: Postponed » Fixed

Recipes can now deploy content. Closing this.

thejimbirch’s picture

thejimbirch commented
Assigned: bsnodgrass » Unassigned

Status: Fixed » Closed (fixed)

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