you can use caveats to accomplish this, by setting...
# spicedb
j
you can use caveats to accomplish this, by setting a caveat where the current time must be before X, and then you pass in the current time on each request
c
Hi there - I am wondering if there is a timeline on when this feature is ready for production use?
https://authzed.com/docs/reference/caveats#defining-caveats In the docs, it seems it is still an experimental feature and not recommended to be used for production yet
v
I believe these are the tasks left to put it out of experimental: https://github.com/authzed/spicedb/issues/386#issuecomment-1404107141
also related to the initial question, as Jake mentioned, you can caveat those relationships so they effectively "disappear" at a specific deadline. But they are still present in the database. For actual TTL that would remove those relationships, we have opened https://github.com/authzed/spicedb/issues/282
c
https://github.com/authzed/spicedb/issues/386#issuecomment-1404107141 so from this issue, it sounds like it actually works in the cluster (without caching), does NOT yet exist in clients and documentation is not complete. is that right? We are hoping to go live within a few months and caveats would be a useful feature for us. I'm trying to get a sense if it will be ready in time for us to go live with.
v
- caching actually landed 3 days ago: https://github.com/authzed/spicedb/pull/1124 - client support should exists (where did you find that?) - documentation could be improved, and we need to to drop the "experimental" tag from it
c
oh great! if the client exists, that would be great. I didn't see it in my first pass of the Go client but i'll check that out again
@vroldanbet would you say it is ready for production use right now in that case? i ask because the documentation says to NOT use it in production
v
we expect one week or two until dropping the experimental flag
c
amazing, that is within our timelines. thank you!
2 Views