thanks, will increase postgres memory and do more testing around it.

yeah I guess that works - i guess notinherited is something manual in the same way noaccess would be? it feels like this could somehow be modelled such that a manual relation isn't required - but i haven't really delved into the implementation so maybe it's non-trivial

well, the big question is: how do you mark an admin as being excluded for the specific resource?

that's a relationship, hence the

notinherited

or

noaccess

it obviously needs a better name than I gave it

I'm having a question about the node client: the RelationshipFilter specifies that only

resourceType

is required. However,

optionalResourceId

and

optionalRelation

are typed as required despite their names. Is it a typing-only issue and I should cast

optionalRelation: undefined as any

, or will I encounter a runtime problem in the client?

that's likely a typing issue

can you file an issue against the node client?

its likely something within the TS generator for proto

Can do!

@User how are you constructing the object?

I think if you use

.create

it'll allow you to avoid the optionals and it'll fill them in with empty strings automatically

Ah, interesting, I don't use

create

. Lemme try

https://github.com/authzed/authzed-node/blob/main/src/v1.test.ts#L29 as an example

Well, it seems that

create

has other (and worse) downsides: it makes all attributes optional 😬

d'oh

okay, well: I'll see if there is a way to mark those fields so that the proto generator makes them optional

but no guarantees; it may not support that

👍 thanks

Arguably, if the v1 API is stable and the generator is buggy, it's worth writing types manually rather than generating them from protos 😁

@User unfortunately, that would be very hard to maintain. The generator is following proto standard (we didn't write it, afterall) and those fields are technically required to be filled in, but most langs just use the default value for strings of

""

. proto3 does have a true

optional

keyword now, but that might result in a wire change and thus, have to wait for a new version of the API

@User Any plans for generating a .NET library?

@User a community member created one a few months back: https://github.com/svickers/authzed-csharp

might be a good starting point to update from

oh thank you

🙂

> those fields are technically required to be filled in, but most langs just use the default value for strings of "" That's fine with me, I'm happy to send

""

if that's what the client expects as an empty value!

Yep, that should work

Is there any special config needed to scale horizontally or can I just add more spicedb instances as needed

@User you'll need to make sure you're using a scalable datastore (i.e. not memdb) and then configure dispatch; ideally, you're using Kubernetes, in which case its just pass the Kubernetes service to the dispatcher config