When working on a recipe, when the script fails to apply (particularly because of existing config that doesn't match) there isn't much useful detail on where the differences are. This can be particularly frustrating when you have just updated the recipe to include configuration just exported from the site itself. It would be great to have an option to have the script cite exactly where it perceives differences.
Either add a separate script or a flag for the existing script, so that the person running the script will get useful output on what specific elements have a mismatch with existing configuration. This could be equivalent to running composer why-not [project].
Active
11.0
Code
Yes, I agree that would be a great thing to have. Currently, whenever the recipe fails to apply there is an error thrown which takes time to find out the exact reason for the failure.
Looks like this is a related one
https://www.drupal.org/project/distributions_recipes/issues/3463641 →
Can we add it to related issues?