Problem/Motivation

#2876085: Before upgrading, audit for potential ID conflicts added the ability for migrations to identify when the migration may result in ID collisions and data loss.
This is warned when running via the UI.
We should warn via drush too.

Proposed resolution

Prompt user to confirm they wish to continue.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

larowlan created an issue. See original summary.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Priority: Normal » Major

I'm not sure if -y by itself is a good idea since 95% of the prompts are "Yes, that is what I said" rather than "Yes, I want to do something dangerous." I got in the (bad) habit of passing -y to site maintenance tasks that incessantly prompt you to things that aren't really risky or disruptive and it's pure muscle memory. I'd imagine many others have the same habit.

Do we have another example of Drush separating those things from badness things? Ideas?

This is probably major; maybe not critical since it's mitigated by Migrate UI being in core but Migrate Drush not being part of Drush core yet. That gives us more points where the site owner can avoid the data loss.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Sydney, Australia
CreditAttribution: jibran at PreviousNext commented

Should we move this to https://www.drupal.org/project/migrate_run as per https://twitter.com/eli_t/status/970366849438420993?

Eli-T’s picture

Eli-T
he/him
Primary language English
Location Manchester
CreditAttribution: Eli-T commented
Status: Active » Closed (won't fix)

Seems reasonable assuming Migrate Run doesn't already do so.

In the meantime, marking this as Won't Fix.