Problem/Motivation
The recipe at /core/recipes/example/recipe.yml isn't a functioning recipe and thus provides a bad example.
It also contains a composer.json file which it doesn't need to.
This was noticed by @jnicola in #3446080: [PP-2] Recipe Browsing UI (comment #10) as it broke recipe discovery.
Steps to reproduce
Try to apply /core/recipes/example
Proposed resolution
Make it a functioning recipe.
Remaining tasks
Fixing it.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 3447994-nr-bot.txt | 89 bytes | needs-review-queue-bot |
Issue fork drupal-3447994
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:
- 3447994-example-recipe-isnt
changes, plain diff MR !8432
1 hidden branch
Issue fork distributions_recipes-3447994
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:
Comments
Comment #3
thejimbirch commentedComment #5
thejimbirch commentedMerge request added. I removed the composer.json file, updated the comments, and made a recipe that can be applied that has the defaults that Drupal core installs so it shouldn't change anything if someone applies it.
I tested it by using it with Drupal quick-start
php core/scripts/drupal quick-start core/recipes/exampleComment #8
josue2591 commentedTesting process
ddev drush si minimalddev drush cget text.settingsand confirm it is 600 (default)ddev php core/scripts/drupal recipe core/recipes/exampleddev drush cget text.settingsand confirm it is now 700After manually testing it I wrote and included an automated test that does the same thing
Comment #9
ltrainComment #10
thejimbirch commentedThis issue is simple enough. Moving to the core recipe system.
Comment #11
ltrainGreat! Just tagging Josué for credit for his review/test.
Comment #12
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #14
thejimbirch commentedHiding MR 138 as 142 is the correct one.
Moving back to Needs Review to please the bots.
Comment #15
ltrainCan we put it back into RBTC or is there something else needed?
Comment #16
mikelutzPosting a relevant slack thread.
Core contrib question: this issue got moved into Needs Work status by a bot. Is there something we can do to get it back to RBTC?
Comment #17
thejimbirch commentedAh, @mikelutz is correct. THe MR needs to be against core, not the D&R project.
Comment #20
mikelutzAlright, lets try that one.
Comment #21
mikelutzCrediting @Josue2591 as he wrote the code. I just opened a new MR against core, cherry picked the commits and (hopefully correctly) fixed some merge conflicts.
Comment #22
mikelutzAlso switching this to major based on "The major priority is used for issues that are not critical, but that do have significant impact or are important by community consensus." As recipes are a hot item right now I would consider having the example recipe be functional for 10.3.0 to be important, but feel free to reduce if I am wrong.
Comment #23
ltrainThanks Mike! Putting back into RBTC.
Comment #24
alexpottI think the example recipe does not need to be tested by the installer... hopefully we can have a simpler test.
Comment #26
akhil babuAdded a Kernel test for the example recipe as suggested in #24. Also updated simple_config_update to simpleConfigUpdate in the example recipe.
Comment #27
b_sharpe commentedConfirmed recipe is functional and only installing optional config when necessary (tested minimal vs standard) since the test is forcing dependencies (search and views). Tests are also passing. RTBC
Comment #28
longwaveBackported down to 10.3.x as it's important to have good examples if people are trying to use this feature in 10.3 or 11.0.
Committed and pushed e9574d73b2 to 11.x and aed5e43a78 to 11.0.x and a225c0a38e to 10.4.x and 38ff4e3ace to 10.3.x. Thanks!
Comment #33
longwave