ECA Migrate: Token support for Plugins

Created on 24 September 2024, 7 months ago

Problem/Motivation

I wanted to use an ECA Migrate trigger to hook into post_migrate events for a specific migration. The event contains the migrate plugin object and its accessible with token but the key properties like `id` are not available.

I suspect this is due to poor token support for plugins.

Note: the ECA documentation says the token is the migration entity, but no such entity type exists - it is a plugin.

Steps to reproduce

Try use "[migration:id]" in a post_migrate event. You can't.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

2.1

Component

Code

Created by

🇳🇿New Zealand Josh Waihi

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Josh Waihi
    • jurgenhaas committed ce36300e on 2.1.x
      Issue #3476548 by jurgenhaas: ECA Migrate: Token support for Plugins
      
  • 🇩🇪Germany jurgenhaas Gottmadingen

    You're right about the migrate token being a plugin instead of an entity. I've corrected the annotation in code which will eventually also be propagated to the ECA Guide.

    In general, the migrate events would do well with some more features. Let's hope somebody is eventually going to define what's needed in detail so that someone else can then implement that.

Production build 0.71.5 2024