Open garethsb opened 6 years ago
The etcd-based implementation uses type and id as a composite key. See https://github.com/bbc/nmos-registration/blob/master/nmosregistration/etcd_backend.py.
This means that a POST to /resource with a duplicate resource id for a different type is currently accepted.
Please tell me we agree these UUIDs need to be truly unique, not unique per type!
Thanks to @rhastie for discovering this issue.
Yes that does seem like a bug. I doubt we've ever attempted to validate that so far.
The etcd-based implementation uses type and id as a composite key. See https://github.com/bbc/nmos-registration/blob/master/nmosregistration/etcd_backend.py.
This means that a POST to /resource with a duplicate resource id for a different type is currently accepted.
Please tell me we agree these UUIDs need to be truly unique, not unique per type!
Thanks to @rhastie for discovering this issue.