We have a migration setup that periodically syncs data from another system to various content entities.
As they're being updated, the rollback action is set to preserve, due to this code in \Drupal\migrate\Plugin\migrate\destination\EntityContentBase::updateEntity:
// By default, an update will be preserved.
$rollback_action = MigrateIdMapInterface::ROLLBACK_PRESERVE;
// Make sure we have the right translation.
if ($this->isTranslationDestination()) {
$property = $this->storage->getEntityType()->getKey('langcode');
if ($row->hasDestinationProperty($property)) {
$language = $row->getDestinationProperty($property);
if (!$entity->hasTranslation($language)) {
$entity->addTranslation($language);
// We're adding a translation, so delete it on rollback.
$rollback_action = MigrateIdMapInterface::ROLLBACK_DELETE;
}
$entity = $entity->getTranslation($language);
}
}
We're not migrating translations, so the translations config isn't set (default to FALSE), which means the if statement above is never true, and therefore the rollback action is always "preserve".
I've scanned the issue queue and haven't seen this reported so not sure if it's a bug, or intentional, but it means unless translations are migrated, content entities cannot be rolled back and deleted.
The only exception I've seen to this is a file entity, as the code above is never called due to the specific class for entity:file migrations.
Active
11.1 🔥
migration system
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Restored the issue template.
After debugging and some more issue queue searching, pretty confident this is a duplicate of 🐛 ID map not copied when cloning row without destination Needs work