migrate_plus.migration_group.games_example.yml in Migrate Google Sheets 2.x
Same filename and directory in other branches
migrate_google_sheets_example/config/install/migrate_plus.migration_group.games_example.yml
File
migrate_google_sheets_example/config/install/migrate_plus.migration_group.games_example.ymlView source
- # A "migration group" is - surprise! - a group of migrations. It is used to
- # group migrations for display by our tools, and to perform operations on a
- # specific set of migrations. It can also be used to hold any configuration
- # common to those migrations, so it doesn't have to be duplicated in each one.
-
- # The machine name of the group, by which it is referenced in individual
- # migrations.
- id: games_example
-
- # A human-friendly label for the group.
- label: Games imports example
-
- # More information about the group.
- description: Simple test of migrating from google sheets.
-
- # Short description of the type of source, e.g. "Drupal 6" or "WordPress".
- source_type: Google Spreadsheet
-
- # Here we add any default configuration settings to be shared among all
- # migrations in the group. For this example, the source tables are in the
- # Drupal (default) database, but usually if your source data is in a
- # database it will be external.
- #shared_configuration:
- # # Specifying 'source' here means that this configuration will be merged into
- # # the 'source' configuration of each migration.
- # source:
- # # A better practice for real-world migrations would be to add a database
- # # connection to your external database in settings.php and reference its
- # # key here.
- # key: default
-
- # As with the migration configuration (see beer_term), we add an enforced
- # dependency so the migration_group configuration will be removed on module
- # uninstall.
- #dependencies:
- # enforced:
- # module:
- # - migrate_example