Currently, configuration installed by recipes is not recognized by Configuration Provider and therefore is not available to other modules that leverage Configuration Provider such as Configuration Synchronizer. See 💬 Is this compatible with Recipes? Active .
Example: using Configuration Synchronizer, examine available configuration updates on a site where recipes have been applied. Result: any upstream updates from applied recipes are not available.
The main implementation challenge is that recipes are not stored locally on the filesystem, so their configuration is not by default available.
Configuration Provider would need to:
Active
3.0
Code
A list of applied recipes is stored in state by the RecipeActivator class in Project Browser → . Taking this approach, supporting recipes would require introducing a dependency on Project Browser and limiting support to recipes installed via Project Browser.