just tested here and subsequent calls are also around 5000ms

that seems slow, even for a call across the planet

yeah, i would expect a bit of latency, but not that much....usage of the API is 200ms, which is fine

if you can get a profile, it might provide some guidance

we can also look into it more deeply on Monday

its quite late here, so signing off for the evening; feel free to add additional info here if you discover something

awesome, no worries. have a great weekend, i will ping you with more information on monday

we're writing an auth service for internal consumers that uses SpiceDB as a backing service, so we're not providing the SpiceDB API directly. we're treating the remove endpoint similarly to the add endpoint, where it's a list of relationships to be removed, rather than a filter/delete request (is the idea that spicedb is modeled after how you delete things in an SQL database?). we're currently turning that single delete request coming into our service as a whole bunch of separate delete requests to SpiceDB, which means that we could end up in a partially applied state if any one of them fails. it'd be nice if we could make them behave more atomically somehow, and ORing together a whole bunch of filters was one way that i thought of doing that. I'm open to other approaches, though, including you convincing me that deleting things one-by-one is a bad idea.

The write call takes in multiple relationships to delete if you have the full rels

ohhh because of

OPERATION_DELETE

. duh. thank you!

Yep!

We are using https://github.com/testcontainers/testcontainers-java to run and test spicedb and I want to share some learnings from the last days. Testcontainers tries to run a shell script inside the container to wait for the container startup, but the spicedb container have no shell inside. So we enabled the http server and check for the http port. The order of the exposed ports is important.

spiceDb = GenericContainer(DockerImageName.parse("authzed/spicedb:latest"))
      .withCommand("serve-testing --http-enabled")
      .withExposedPorts(8443, 50051)
      .waitingFor(Wait.forListeningPort())

Also it was important in the java-sdk to use explicit no tls (ManagedChannelBuilder.fortarget(endpoint).usePlaintext()) the default in sdk is with tls. Now we are very happy with the solution and startup time 🙂

Hi folks. I have a use case where I need to watch for user permissions. I.e. When a permission changes for a user I need to notify someone. Is it possible to anything like that? I now there is the watch for relationship but that only allows to listen to direct relations but I need to watch for the evaluation of a permission for a user. Not sure that makes sense ...

Thanks Joey! Does look like what I need. Whats the current status? Seems has been closed but reopened and still some work on it?

the closed was just a different PR; the pieces of it have been in active development for the past few months with the next piece (LookupSubjects) in early review now

any estimation when it would be available?

nothing concrete, but once LookupSubjects goes in I hope to start on an alpha implementation shortly thereafter; the big open question isn't when we'll have something that works, but rather when we feel confident enough that it has met sufficient scale to be declared open/ready for all install sizes

I hope that LS will be going in a week or two, with a followup to enable the API itself shortly thereafter

Lookup API response is not easy to parse, if more than one resource, it does not provide any common root {"result":{"lookedUpAt":{"token":"GgQKAjE1"},"resourceObjectId":"topsecret1"}} {"result":{"lookedUpAt":{"token":"GgQKAjE1"},"resourceObjectId":"projectreport1"}}

LookupResources

is a streaming API, so it will return results as distinct items

Hmm i see, How do you suggest to collect the response and process it ?

depends on the language you're using, but either a callback, or a for a loop

Java

For synchronous processing the generated blocking stub will return an Iterator for the response (https://grpc.io/docs/languages/java/basics/#server-side-streaming-rpc-1). For async, the Client-side streaming RPC example on that page has an example using StreamObserver that can be adapted

Thanks Sam, any example with REST API ? That would be really helpful for me.

I am trying to add gradle dependency, 'com.authzed.api:authzed:0.2.0' , Java example does not compile with it

I am trying to compile this one, https://github.com/authzed/authzed-java/tree/main/examples/v1

implementation group: 'com.authzed.api', name: 'authzed', version: '0.2.0'

I am trying to add gradle dependency com