- 🇨🇦Canada ergonlogic Montréal, Québec 🇨🇦
See ✨ Avoid spurious updates to UUID in `system.site` Active
In looking through the code, it's not clear why \Drupal\config_enforce\ConfigEnforcer::generateHashFromActiveConfig() and \Drupal\config_enforce\ConfigImporter::handleSpecialCaseConfig() single out the system.site configuration to preserve the uuid.
Apply eyeballs to code.
Document the reasoning in the code as comments/docblock.
After some poking and prodding an a bit of serendipity, it looks like Drupal core uses this specific config's uuid as a proxy for detecting whether the entirety of the config sync directory is from the current site (or a clone of it) or from a different site. If the config has a different uuid, core refuses to import the config and shows a message that the config is not from the current site or a clone of it.
It looks like this was added as part of
#3175060: [meta] Refactor internals →
in commit 707e6736 by
@ergonlogic →
.
Add documentation to code.
None.
None.
Active
1.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
See ✨ Avoid spurious updates to UUID in `system.site` Active