alright cool, I think my main thought was whether we should try and keep the

user {}

definition empty or not

totally up to you

it really is about how you intend it to read

seems pretty good

alright awesome, thanks!

one of the really nice benefits of all subjects being their own definitions is that you can do cool stuff like add permissions for some subjects onto others 🙂

Is there some way to debug where is the issue located?

turn on trace logging in SpiceDB via

--log-level=trace

and see which query is timing out

and then see if it happens when you run it yourself in Postgres

Thanks, I'll try to debug

Hello, In which data center in the EU is the SpiceDB Dedicated Managed Service offered? Regards Andreas

Any AWS or GCP regions

I would also be interested in the status regarding ISO27001 and SOC2.

hi there, i'm looking to do a bulk permission checks for a single resource and subject, and returning a list of permissions the subject has access to in the resource. Is

LookupResources

the way to go?

currently working on SOC2; @dsieczko

single resource and subject, or single permission and subject?

single resource and subject. given a subject, i want to get a list of permissions the subject has access to in a specific resource

for that you'll need to just issue the checks

LookupResources is, as its name implies, for finding the resources on which a given subject has a specific permission

just issue the checks for each permission in parallel

gotcha, thank you

if you are using an RBAC-like schema, you can also use a Read to get the actual relationships

It looks like I have this issue when all traffic goes through pg-bouncer. I wonder if you expect to have a bouncer. in spicedb + postgres setup?

not usually, no

its possible your bouncer is limiting connections

although I'd still be curious to know why its causing that issue

It kind of feels like a cold cache / thundering herd problem

on the connections from the bouncer?