Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
In #3427558: Output information from the recipe application process, we added output from the recipe application process. However, it does not appear that that we output any information about what is happening when we get to the config section of the recipe, nor the importing config from the /config folder.
Steps to reproduce
Apply a recipe. You will see output from:
- Progress bar of applying the recipe
- Recipes applied
- Modules installed
- Themes installed
- Content created
Verify you don't see output from:
- config folder being imported
- config:import
- config:actions
Proposed resolution
Add additional messaging.
Remaining tasks
Doing it
User interface changes
N/A
API changes
TBD
Data model changes
TBD
Comments
Comment #2
thejimbirch commentedComment #3
ashrafabed“I had to use a debugger to figure in some cases why the configs changed and why it was unhappy about it.”
This (slack) comment was in relation to recipes defaulting to strict: true as part of a conversation about whether that should continue to be the case.
Based on my (brief) exposure to the issue via that conversation, I felt that “strict: true” was not the problem, the problem was the lack of visibility into whether all configs from a recipe were actually applied.
So I recommend displaying some sort of notice to explain how config was applied. For example, “Configuration for the following modules was/was not overridden because X”
I wish I could give a more specific recommendation, but I’m not prepared to at this time (would need to explore the issue more first)
Comment #4
berdirBoth can be true. strict: true by default being a problem and causing all kinds of issues, and not having useful output.
> “Configuration for the following modules was/was not overridden because X
This kind of what you get with strict: false actually. It proceeds and skips certain configs. And yes, I agree that this could be useful, but it could also be a lot and it's very technical. Maybe just for drush/core command. Maybe with an optional -v argument?
strict: true throws an exception currently and tells you just that config foo doesn't match and the whole process aborts. (no "because X"). I think it should then essentially show a diff between those configs.
Comment #5
thejimbirch commented