Problem/Motivation

The Recipe Authoring guide offers no info on how to easily capture configuration into a recipe.

If they're lucky, one might search for ways to use Drush to capture single config exports and may find they can arrow

drush config:get some.config > recipes/my_recipe/config/some.config.yml

.

They might even come across how they might use the yaml:unset:key Drush command to clean up uuid and _core entries.

Proposed resolution

Document these as proposed methods to capture config into a recipe.

Comments

jcandan created an issue. See original summary.

jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented

My procedure is to configure $settings['config_sync_directory'] = '../config/sync'; and commit an initial drush config:export.

Then create new configurations (e.g. create a content type, field, etc.), export config, and monitor git status for changes.

Then, finally, use the config:get and yaml:unset:key commands to export cleaned versions to the recipe I'm working on.