Contents
What is the source key of the migration plugin?
The source key of the migration plugin defines which source plugin the migration uses. The value is an associative array containing the name of the source plugin and the configuration for it. Some source plugins might not have any configurations. The code snippet below is part of the Drupal 6 to Drupal 8 node migration definition.
What are the process plugins for Drupal migration?
List of process plugins provided by the contributed Migrate Plus module. Examples on how constant values can be defined in the migration. Instructions and references to relevant APIs for writing your own process plugins. The contributed addressfield process plugin transforms Drupal 7 Addressfield values to Drupal 8 Address values.
Which is the process key of a migration?
Do not add the documentation page to this guide before the process plugin has been committed to the contributed module. The process key of a migration describes, property-by-property, how the destination is to be constructed from the source data. List of process plugins provided by Drupal core modules.
What does track changes do in Drupal migrate?
Setting the track_changes option to TRUE will cause each incoming source row to be hashed and, if previously imported, compared to the previous value to determine whether the item should be re-imported. This is used to import changed as well as new records from the source.
How to extend the API in custom migrations?
There are two ways to extend the API: Using the Sql () method, or by defining custom MigrationOperation objects. To illustrate, let’s look at implementing an operation that creates a database user using each approach.
Which is the source plugin for Drupal 8 migration?
The code snippet below is part of the Drupal 6 to Drupal 8 node migration definition. It defines that the migration uses the ‘d6_node’ source plugin. Drupal 8 core and contributed modules provide several source plugins for most common use cases, for example migrating from CSV, JSON or XML.
How to decouple custom migrations from SQL?
To decouple the custom operation from the SQL, you can define your own MigrationOperation to represent it. The operation is then passed to the provider so it can determine the appropriate SQL to generate. With this approach, the extension method just needs to add one of these operations to MigrationBuilder.Operations.