Migrations in Drupal can be performed into every kind of entity types. The module is a great helper to set default values, if the entry is a new one. This solves the challenge we have, that an update migration is always overwriting the value.
As far as I can see there is no need to tie this feature to nodes only. The whole functionality itself can be easily entity agnostic, so support for example taxonomy terms or user migrations as well, because all of them can be reached via the entityTypeManager.
Make the module entity agnostic.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
szeidler commentedHere's a try. Thanks for reviewing.
Comment #6
jnicola commentedLooks good to me, and yeah come to think of it there really isn't a reason it can't be entity agnostic!
Merging.
Glad someone else ran into this same issue and found it helpful. I not only found it maddening to deal with, but when I have explained it to others they just assumed I didn't do something right or didn't know what I was talking about!
Comment #7
jnicola commented