They'll be used while a developer is working on a feature. That can vary between a few hours to a few days.

gotcha

ok

so we have a file format you can download from the playground

that contains both schema and test relationships

But everyone understands that these environments are best-effort. They can go away if they leave these unattended for a while and we have ways to re-deploy them if we clean them up if someone left them unattended.

Ah that's a good idea.

we're working on adding support for it to

zed

, so you can do

zed import filename.yaml

and it'll load everything into a SpiceDB

but, we also support that file format in SpiceDB on the test server: https://github.com/authzed/spicedb/blob/main/cmd/spicedb/testserver.go#L194

so what you'll likely want to do is

create that .yaml, either manually or via playground

then specify its path as

--datastore-bootstrap-files=path/to/file.yaml

which will start SpiceDB and then load the schema and test relationships into the install

as for which datastore type to use, that's your call

if it is a single node for just local dev/testing, maybe just use the memdb datastore

with the caveat that if it goes away, any other data you've written will go away

but that's probably ok

@User unless you need similar performance too?

Is there a way we could

zed export

from an instance? The use case I'm thinking of is that our QA team sets up data for different use cases in a "permanent staging" instance. When we open a PR we start with an environment pre-loaded with a bunch of these test accounts for different use cases and we can test a feature by logging in from the point of view of different users with different access levels. If possible, it'd be nice if the QA team can keep adding different use cases on the "permanent staging" instance. Opening a new PR environment comes pre-loaded with both the test application data and SpiceDB relationships required to enable access.

there is

zed schema copy

for schema

we don't (yet) have

zed relationships copy

, but it would be fairly simple to add

then you could just call those two

that would be awesome

or we add a

zed export

to the file format

we'll file some issues

would be a good starter project too if you have some time 😄

Awesome, thanks Joey. I'll try to dig around a bit when I have some time. Really excited about all your work on this problem. A year ago my boss asked me to look into solving the Authz problem across services. I told him "At google we had Zanzibar, I bet someone has already made a SaaS can use". I was glad I found you all are working on the problem. We might not have to implement the hacky solution I'd comen up with.

ids-and-best-practices

@User that's why we're here 🙂

We still see intermittent "DEADLINE_EXCEEDED" errors on API requests. Setting the timeout on the GRPC client does not seem to help.