recipe.yml
File
-
core/
recipes/ example/ recipe.yml
View source
- # The name of the recipe.
- name: 'Example'
- # The description of the recipe.
- description: 'Provides an example recipe.'
- # The type key is similar to the package key in module.info.yml. It can be used
- # to group Drupal recipes.
- type: 'Content type'
- install:
- # An array of modules or themes to install if they are not already. The system
- # will detect if it is a theme or a module. During the install only simple
- # configuration from the new modules is created. This allows the Drupal recipe
- # control over the configuration.
- - node
- - text
- config:
- # A Drupal recipe can have a config directory. All configuration is this
- # directory will be imported after the modules have been installed.
- # Additionally, the Drupal recipe can install configuration entities provided
- # by the modules it configures. This allows them to not have to maintain or
- # copy this configuration.
- import:
- text:
- - text.settings
- # Import all configuration that is provided by the node module and any
- # optional configuration that depends on the text module that is provided by
- # modules already installed.
- node: '*'
- # Configuration actions may be defined. The structure here should be
- # entity_type.ID.action. Below, text.settings is updated to set the default
- # summary length for text fields to 700 characters.
- actions:
- text.settings:
- simpleConfigUpdate:
- default_summary_length: 700
- # A Drupal recipe can have a content directory. All content in this directory
- # will be created after the configuration is installed.
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.