A follow up to #2711353: Migrate never unsets existing data for content entitites to do the same for config entities.
This is the IS from that issue:
If the source ceases to have data , this is never reflected in the destination. There are two problems (at least), this patch attacks the field level in the content entity base, config entities and raw config entities are also broken but probably needs to be different issue and less severe because this only comes up in reruns, the migrate_drupal path does not really support reruns. And then there is the case when a whole row / entity disappears but that is an entirely different issue.
The patch in that issue dealt with allowing NULL values as a valid source using MigrateExecutable::setEmptyDestinationProperty($destination)
.
Comments
Comment #3
rakesh.gectcrComment #7
heddnIs this about deleting config entities if the source data goes away?
Comment #8
quietone CreditAttribution: quietone as a volunteer commentedI think it is about allowing NULL values in the source and migrating them correctly to config.
Comment #16
mstrelan CreditAttribution: mstrelan at PreviousNext commentedAdding some tags.