Hi, How do I evaluate request paths instead of uni...
# spicedb
d
Hi, How do I evaluate request paths instead of unique IDs? For example two organisations can have the same name for a repo but the allow and deny is based on the path instead of the repository name.
v
👋🏻 sounds like a scenario for SpiceDB caveats. You can provide the request path as part of the
CheckPermissionRequest
context
and store the "expected request path" as part of the stored relationships context for your
Organization
.
check out our caveats docs: https://authzed.com/docs/reference/caveats