Thank you so much Jake for your help!

You’re welcome!

Folks, have been playing with the authzed playground for a couple of days, have got the hang of it now. Been thinking about how I could implement access rules that incorporate some element of the environment such as time or maybe location. Ofcourse one way is to evaluate the env based rules outside of authzed and add/remove authzed relations accordingly. But this seems clunky. Is there a more natural way to address this?

Just came across this message in the Zanzibar community history. This sounds like exactly what I am looking to do https://discord.com/channels/844600078504951838/910689733192056852/950816354326417418

yeah, caveats is the proposal for dynamic/environment-specific information

feel free to add your use cases to it

Getting an odd error using zed 0.4.2

$ zed permission lookup github/repository read github:user:1234
Error: the length of the unpacked is not equal to the provided input

Also getting the same error with

check

. Any suggestions?

does a non-zed API call work?

I can try that. schema reads and writes do work.

schema read/write works from zed?

any errors on the SpiceDB side then?

SpiceDB doesn't seem to be even be registering the request in the log

strange

maybe some sort of proxy is intercepting the request somehow?

yep. Well, I'm already in the debugger, so I'll poke around.

Hi all! We've had SpiceDB set up in a Kubernetes cluster for a while now, but we're finding that when we are rolling over the deployment, a small number of calls to SpiceDB seem to get

UNAVAILABLE: End of stream or IOException

errors in that time period. We've been careful to configure our client facing load balancer to time its drains and terminations appropriately, so we're curious what this might be caused by... If I had to guess, I would say it might be pods being terminated before completing dispatch requests, but I'm not 100% sure...

there's probably a mismatch between your pod termination grace period and the

--grpc-shutdown-grace-period

flag on spicedb

ah, gotcha -- will look into that, thank you!

getting somewhat back to this. A

grpccurl

call was successful. Very odd.

weird

maybe your zed is misconfigured somehow?

either that or somehow zed became incompatible, but it should be fully backward and forward

what version of zed are you using?

0.4.2. I seem to be the only one having this issue so far, so let me spend a little time on it.

ok

Is there a typo in the command?

github:user:1234

->

github/user:1234

?

If so, it might be that zed can't parse the subject correctly because it splits on

:

to get the object and id

just a quick followup on the otel issues i was having yesterday in case anyone else is trying to integrate with newrelic: the otel sdk as of spicedb 1.6.0 is too many versions behind and newrelic seems not to understand the payload. running spicedb main with cobrautil also bumped to main successfully delivers traces to newrelic

are there any properties of zed tokens that can safely be assumed by a consumer of the api? like, can they be sorted by recency by inspecting the contents? or should they be treated as totally opaque

totally opaque