Problem/Motivation

Given the exiting new recipe feature in core, it would be very nice if this module had a command similar to config:devel-export but exporting to a recipe folder.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork config_devel-3472623

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

kopeboy created an issue. See original summary.

mortona2k’s picture

mortona2k commented

This is a great idea. This tool works great for themes/modules/profiles. Makes sense to support recipes as well.

thejimbirch’s picture

thejimbirch commented
Issue tags: +Recipes initiative
richardgaunt’s picture

richardgaunt commented

Looks like the `extra` property in the `recipe.yml` can be used to contain the configuration to be exported.

So the recipe for config_devel could look like the following to incorporate this feature:

name: 'Test recipe'
extra:
  config_devel:
      - block.block.test1
      - block.block.test2

Note: the no type - install / optional as recipes don't have this concept (all install i guess).

richardgaunt opened merge request !12

richardgaunt’s picture

richardgaunt commented
Status: Active » Needs review

Made a first attempt at this - writing configuration works but importing back from config directory to active storage does not work but this seems to be an issue with the module.

niklp’s picture

niklp commented

+1 for this as a thing

joachim’s picture

joachim commented
Status: Needs review » Needs work

I'm not keen how messy recipe support is making things -- lots of special cases.

Are recipes not handled by Drupal core's extension system?