right now you can either use the parser we have in the Go package (if you are in Go), write your own parser, or wait for the reflection API stuff: https://github.com/authzed/spicedb/issues/439

hello, I was looking for example

DeleteRelationships

for NodeJS, and could not find one. Wrote something myself - please see below. Does it look right?

const deleteRelationships = v1.DeleteRelationshipsRequest.create({
        relationshipFilter: v1.RelationshipFilter.create({
          resourceType: kind,
          optionalResourceId: id,
          optionalRelation: role,
          optionalSubjectFilter: v1.SubjectFilter.create({
            subjectType: 'user',
            optionalSubjectId: user
          })
        })
      });

there is also this PR: https://github.com/authzed/spicedb/pull/657

@Sam ^

I am on java, I can write my own parser, is there any basic design/ rules that I need to follow?

Has anybody used SpiceDB with GraphQL? In our current co-located authorization system we do a check on every element in the GraphQL response. If we did a direct port to SpiceDB, this could potentially lead to some queries making numerous calls to SpiceDB potentially adding significant latency. Curious if anybody else has run across this and has any tips.

what is the timeline on this? if it is soon-ish, we can look into getting reflection APIs added

the problem with writing your own parser is that it will have to be adjusted when we add new things to schema

the general recommendation is to run the checks in parallel

Yes we are looking for sooner may be in next 1-2 month.

can you add your requirements to the linked issue?

Sure.

There's no way to batch checks is there?

gRPC runs checks in parallel

Does the operator allow you add arbitrary annotations to the spicedb deployment?

Hi, I'm trying to set a context with the

zed

tool, but when i'm running it I get

Error: token does not exist

no matter what are my input. I used that command without trouble previously but I recently switched to a new machine and it doesn't seem to be working. I'm on an m1 mac and I just installed zed with homebrew. Do you have an idea of the problem? Thanks 🙂

@Alex J did you recreate the context on your new machine? tokens are stored in the keystore, and if you moved to a new machine, the token itself may not be present

I'm actually trying to create the context. My command is

zed context set test localhost:50051 my_super_token --insecure

what does

zed context list

show?

It shows

Error: config did not exist

. I manually deleted it (in ~/.zed/) after I got the same error and tried to reinstall the homebrew package but apparently it's still missing. What would be the proper way to re-create it?

The config only stores the current context, so a

zed use

or

zed context use

I think will bring it back

I can open a PR to fix the error message -- it should just tell you that you don't have a context selected

I see. The problem still remains though - I cannot create a context to use 🤔

what error are you seeing when you run

zed context set

?

I'm getting

Error: token does not exist

. I'm currently looking into the code (I checked out the latest) and what seems to happen is that the token is not properly set in the keychain in the KeychainSecretStore.Put so when it tries to read it back right after this call it fails

Could it be a macOS setting somewhere to allow the terminal to access the keychain or something?

every time a binary tries to access the keychain, you should get a popup asking if you'd like to allow it once or forever

i wonder if for some reason it's being rejected