"""
If you use /v1/resource/generic/<blah>, you'll get <blah> (after the server or client translates it to an uuid5 _if_ it <blah> is not an UUID).
The problem this bug is about is that when <blah> is a string "blah" it's converted to a uuid5("blah") and that is always the same, whoever you are. That's cool, but you cannot have several resources with "blah" as "original-resource-id". Which is what the bug is about.
"""
so is this still the same assumption then? if you provide a uuid, then it automatically becomes primary resource_id and therefore no 2 projects may pass in same uuid?
""" generic/ <blah>, you'll get <blah> (after the server or client translates it to an uuid5 _if_ it <blah> is not an UUID).
If you use /v1/resource/
The problem this bug is about is that when <blah> is a string "blah" it's converted to a uuid5("blah") and that is always the same, whoever you are. That's cool, but you cannot have several resources with "blah" as "original- resource- id". Which is what the bug is about.
"""
so is this still the same assumption then? if you provide a uuid, then it automatically becomes primary resource_id and therefore no 2 projects may pass in same uuid?