Contrib.social

Recipe validation should consider modules that are available, not just the ones listed in recipe.yml

Open on Drupal.org →
Created on 27 September 2024, about 2 months ago

Problem/Motivation

Right now, the recipe system validates everything in the config.actions section of recipe.yml, trying to confirm that every module mentioned in that section (i.e., in the prefix of the config entities' names) is listed in the recipe's install list.

That's flawed -- the recipe might rightfully be expecting that module to already be installed, either by the site at runtime, or by a dependent recipe.

Steps to reproduce

Have a recipe that uses config actions to make changes to a user role, but don't list User in the recipe's install list. You'll get a validation error as soon as you try to instantiate this recipe.

Proposed resolution

The validation needs to be a lot better - when compiling the list of modules to compare against, it needs to consider the following things:

  • The recipe's install list
  • The install lists of any recipes that the current recipe depends on
  • The currently installed modules
🐛 Bug report
Status

Active

Version

11.0 🔥

Component

recipe system

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024