Companion patch to #2535458: Dispatch events at key points during migration, demonstrating how the event approach enables contrib to do a bunch of stuff without specific support in the core migrate API. It may ultimately be broken up into individual features, but for now it's convenient to pull together here. Potentially supercedes a few different other issues, such as #2432993: Implement reporting of results on migrate-import.

Comments

mikeryan’s picture

StatusFileSize
new4.73 KB

To get started, a reroll of #2432993: Implement reporting of results on migrate-import implementing statistics reporting.

mikeryan’s picture

Related issues: +#2429107: Display last imported time with drush migrate-status
StatusFileSize
new8.08 KB
new3.99 KB

This adds support for last imported time (#2429107: Display last imported time with drush migrate-status).

mikeryan’s picture

Related issues: +#2432985: Implement --feedback option on migrate-import, +#2432983: Implement --limit option on migrate-import
StatusFileSize
new17.83 KB
new12.78 KB

This implements --limit and --feedback using the proposed pre/post-save events (well, actually it just uses post-save). I also moved the code handling time and memory limits from the core MigrateExecutable to migrate_tools, but that's not fully integrated yet.

mikeryan’s picture

StatusFileSize
new17.91 KB
new2.56 KB

Updates to reflect latest core patch at https://www.drupal.org/node/2535458#comment-10139648

mikeryan’s picture

StatusFileSize
new18.76 KB

Letting migrate-manifest use the extended MigrateExecutable.

mikeryan’s picture

Version: » 8.x-1.x-dev
Status: Active » Fixed

All the pieces of this were done in the context of other issues.

Status: Fixed » Closed (fixed)

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