I'm seeing what feels like an oddity around UUIDs for pathauto pattern configurations, resulting in complexity around our config/code versioning workflow.
Every time a pattern is saved.
UUID visible in the export steps remains consistent.
The UUID is different, and is regenerated each time the pattern is saved.
This may be expected behaviour but it's causing us some workflow and config sync issues. (Although once we've stabilised our patterns it won't be an ongoing problem.)
We've been working around it in the meantime by generating UUIDs in production and manually replacing them in our local code before committing, but I'm worried this may have unintended consequences.
Needs review
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Added change to \Drupal\pathauto\Entity\PathautoPattern::addSelectionCondition() which persists the UUID if the configuration includes a uuid property saving the need to regenerate a unique UUID everytime.