We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
Yes that does seem like a bug. I doubt we've ever attempted to validate that so far.
Sorry, something went wrong.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: