completed

but its mostly designed for internal use; Authzed.com, for example, doesn't support it as part of the SaaS API

I hear you but I've got all of this reactive machinery and suddenly it has nothing to do 🙂

calculating all affected permissions is a very hard and heavy problem

its not a scalable solution

that being said, nothing precludes you from just re-running all needed checks anytime a relationship is changed

and then just updating your UI accordingly

I understand ans am not complaining, just trying to figure out a path forward

probably that ^

you just define the N number of checks your UI needs

run them in parallel anytime a relationship changes

and emit the results

Got it. That gives me plenty to chew on for today. Thanks for responding so quickly on a Sunday

anytime

one thing to note is that SpiceDB/Authzed are designed to scale for many parallel checks

so doing a bunch of them in parallel should be fast

and you'd only do so for your "active" users via websocket

That's a good and welcome point

Hi, I am looking deeper into SpiceDB offerings, and I'm not sure if I am missing something, or it's not really possible to create a dynamic role->permissions authorization schema? Taking example from GCP IAM, AWS IAM, etc.

@User yes, you can define a data-defined role schema; the specifics on how dynamic you can make it really depends on your use case

As far as I could tell, the only way I could do this is by modifying the schema (as per the example on the blog post)? What if I wanted the end-users to be able to define custom roles, I would have to modify the schema every time?

you can define the roles themselves as objects

This "user defined roles" article would be useful in the docs (at least as a link), it's what gave me confidence that SpiceDB could functionally handle whatever future requirement would get thrown at me 😄

Hi! I am having an issue with using the HTTP REST module. Any requests return this error response:

connection error: desc = \"transport: Error while dialing dial tcp: missing address\

with status code 503 Looks to me like a small misconfiguration, but I set nothing but

spicedb serve --grpc-preshared-key "<somesecret>" --http-enabled

Hi, we are finding we need to call

WriteSchema

each time we start a SpiceDB node or we get errors that object definitions don't exist; is the schema or some part of it not stored in postgres?

I don't have this issue (with Postgres too) @User, so I assume something is indeed wrong

OK I'll report back... our infra guy noticed this.

@User are you using Memdb datastore by accident?