Follow-up from. We've removed the expectation that UUIDs should be in default configuration as well as the usecase they were intended to support (deploying configuration between arbitrary sites) in favor of having a single site UUID. So, if a module does provide a UUID in a default config file, we need to decide what to do with it.
There are three options:
- Throw an exception.
- Ignore it.
- Respect it and install with that UUID.
Throwing an exception would be best because it avoids the problem of accidentally supported usecases that got us into the UUID snafu in the first place. :)
Shouldn't be any.