It's an edge case, but a different migration plugin class from the default can be specified in migration configuration. A core example from d6_profile_values.yml:

class: Drupal\user\Plugin\migrate\ProfileValues

class is not defined in the configuration schema, thus attempts to export and import migrations using it (as in migrate-upgrade's --configure-only) drop the class configuration. We need to add it to the schema.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeryan created an issue. See original summary.

mikeryan’s picture

Status: Active » Needs review
FileSize
427 bytes
mikeryan’s picture

Version: 8.x-3.x-dev » 8.x-2.x-dev
FileSize
1.09 KB

Is 'class' now required?

mikeryan’s picture

Once more.

  • mikeryan committed a931fec on 8.x-3.x
    Issue #2819901 by mikeryan: Add 'class' to migration configuration...

  • mikeryan committed 42af79d on 8.x-2.x
    Issue #2819901 by mikeryan: Add 'class' to migration configuration...
mikeryan’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.