1 # Migration configuration for {{ plugin_id }} content.
3 label: {{ plugin_label }}
4 migration_group: {{ migration_group }}
6 plugin: {{ plugin_id }}
8 # Specify the destination plugin (usually entity:entity_type).
9 plugin: {{ destination_plugin }}
11 # Hardcode the destination node type (bundle) as 'migrate_example_beer'.
14 default_value: migrate_example_beer
24 field_migrate_example_country: countries
25 field_migrate_example_beer_style:
29 # Some Drupal fields may have multiple components we may want to set
30 # separately. For example, text fields may have summaries (teasers) in
31 # addition to the full text value. We use / to separate the field name from
32 # the internal field value being set, and put it in quotes because / is a
33 # YAML special character.
35 'body/summary': excerpt
36 # Our beer nodes have references to terms and users, so we want those to be
37 # imported first. We make that dependency explicit here - by putting those
38 # migrations under the 'required' key, we ensure that the tools will prevent
39 # us from running the beer_node migration unless the beer_term and beer_user
40 # migrations are complete (although we can override the dependency check by
41 # passing --force to the drush migrate-import command). We can also add
42 # 'optional' dependencies - these affect the order in which migrations are
43 # displayed, and run by default, but does not force you run them in that
45 # The general rule of thumb is that any migrations referenced by migration
46 # process plugins should be required here.
47 migration_dependencies: