Force-create new UUIDs in default config objects during initial import/creation

Created on 21 December 2013, almost 11 years ago

Updated 7 June 2024, 5 months ago

Default configuration files of modules may contain UUIDs from the originating site on which the config was created.
These UUIDs of newly created configuration objects are not universally unique, but identical on all sites instead.

Force-create a new UUID for each configuration entity object that is imported from default configuration during initial installation of an extension.

Given this and other existing diverging behavior of the default config import process:
1. The original assumption that the default config import vs. the active/staging store synchronization would be the same is no longer really true.
2. Next to custom business logic like force-creating new UUIDs, the default config also uses a single, non-swappable file format.
3. It's probably time to decouple of the default config import code from the config syncing code. Which probably allows us to kill the new isSyncing() flag, too.

📌 Task

Status

Needs work

Version

11.0 🔥

Component

Configuration entity →

Last updated 34 minutes ago