- Issue created by @bibliophileaxe
- π¨π¦Canada bibliophileaxe
There is an open issue in the Features module for supporting recipe generation: https://www.drupal.org/project/features/issues/3303481 β¨ Support generating recipes Active
- π§πͺBelgium svdhout
https://www.drupal.org/project/config_patch β provides a framework for providing patch files for config (the differences between active configuration and sync configuration).
It is plugin based, creating a output plugin for recipe creation could be a good approach here.
- π΅π±Poland grzegorz.bartman
For one of our projects ( https://www.drupal.org/project/openintranet β ) we created a helper module that allows to export config as recipes. It is not perfect but perhaps someone will use it https://www.drupal.org/sandbox/jaro2801/3523096 β
- πΊπΈUnited States mortona2k Seattle
I have been happy with Config Devel for updating install/optional config in my custom modules.
You list the config you want to export in the module's info file, under config_devel: install/optional, and then run
drush cde
(config devel export). That will export your site's config that is listed into the module's config directory.This issue is for allowing Config Devel to export to recipes: https://www.drupal.org/project/config_devel/issues/3472623 β¨ Allow writing configuration to recipe's config directory Active
- πΊπΈUnited States emofsnead
Another option if you use a Git workflow is utilizing the config_split module with the yml files set the way you want them in each environment and the config_suite module automatically import and export settings set to the workflow preferences. I am automatic true for import and export except βstagedβ where I have export to false so you release after testing. If you have a team you may tighten that flow so the actions never have a risk of tripping over one another.