I think this is probably related to 3436581 🐛 Layout builder content blocks are duplicated on import Needs work , but it's more in the vein of a question.
When importing an export package (yaml and assets in a zip), what happens if there are entities (nodes) that already exist in the destination environment, that "match" the import? This could also apply to running the same import twice.
Does it use UUIDs to decide whether to create or update? Or does it simply create entity new every time, producing duplicate entries?
The question arises in my case because we cloned a production site a while ago to create a bunch of new content "behind the scenes" as it were, a fair portion of which is meant to update existing content, as well as creating a whole bunch of new menus and terms. On "go live" this needs to all get imported correctly back to production.
I guess the same question would apply to the assets.
Active
1.4
Documentation
Sorry. I just reread the actual project description, and I think the question is answered right up front. It's described as using UUID to make the create/update choice. I presume this also means that there won't be data collisions if node IDs from the source match node IDs in the destination, but UUIDs don't.
Closing.