it isn t yet but its planned
# spicedb
j
it isn't yet, but its planned
b
Is there any current thinking on how thise would be implemented? Caveats are just json blobs, right? Would some json field name be chosen as "special" to run expiration GC against?
j
probably a specialized type
and then it would be pulled into a new column potentially on the relationships table, which would then be used by GC
d
Likely would need to be, otherwise how would the spicedb GC process know what to look for for deletion hints
yup 🙂
j
the caveats system supports definitions of new types really easily
so having a custom
expiration
type, and giving a context variable that type, is easy
either that or we have a built-in caveat ala
relation foo: user with expiration
that's the still TBD part
2 Views