Yeah, that bit makes sense 🙂

One sec

if so, we'll add additional error catching around the GA

it is supposed to fail safe

for exactly the people who do block it

It now appears that I send the GA bits, but I still get the same error+reload. The Amplitude call still appears to fail for some reason

@calle-ibx what is your organization id?

Back in March it looks like (yes, it's been a while since I updated zed) there was a change in the zed schema.go to error out if more than 1 namespace was found in a schema file on a write and copy. Was this check put in there because it's a "bad thing to do in spicedb" or as a sanity check for authzed? i.e. if it's the latter and I go about reading/writing the schema outside of zed into spicedb with multiple namespaces will bad things happen?

can you clarify what you mean by "more than 1 namespace"?

multiple definitions are allowed in a schema

where there will be multiple definitions such that it is

company/users company/ldap_groups serviceA/accounts serviceA/items serviceB/api_keys

ah

it was a sanity check added for authzed, since it doesn't allow for more than one prefix

we'll probably need to relax that on the zed side

sweet thanks. so not "a bad thing".

nope

the prefixes are purely a convention in SpiceDB

Authzed is the only one that enforces them

do you mind filing an issue on github.com/authzed/zed about this?

we'll take a look at reducing the restriction

Yup, I can go file an issue.

THanks

On this issue of prefixes, is there a robust way to add/delete definitions according to a prefix? We're deploying a development instance and would like to have our CI pipeline append policies specific to each feature branch, then tear them down when the branch is destroyed. The current plan is to do this with a python script and limit it to 1 concurrent job, but is there a better way?

Hi guys, I am doing a small service in typescript that communicates with a locally running spiceDB instance. Of course I am using your node client, and I have been able to communicate with the spicedb following the example in the package github page (for node). As it is the first time I am doing anything related with gRPC protocol I have to admit that I am struggling understanding the specification and how to translate that specification to the usage of your module. My question would be, do you know any resources that might help me understanding or should I just shoot my questions here?

you want to use prefixes to represent each feature branch for stage or prod or...?

The .test.ts files in here can provide some guidance: https://github.com/authzed/authzed-node/tree/main/src

but feel free to ask additional questions here as well

thanks, I'll take a look to them and ask if necessary (I was so focused on reading the code that I forgot that test are there to help you 😉 )

we definitely do need more examples though, so if you find anything lacking, let us know and we'll add them