but you'll need to do the recursion yourself

gotcha

Hi, is there an easy way to create a backup of all relationships?

I don't think this is a thing in Authzed Serverless, but I think it is in Authzed Dedicated. You'll have to create your own backup routine. You can basically do

ReadRelationships

ver all types of your schema, and them use

at_exact_snapshot

to lock at a specific snapshot of the state of the underlying permissions. @Jake is has probably more context around backups

In the Authzed app, I get a warning "Google Cloud Platform Google Compute Engine: Partial Outage". What exactly does that mean? It seems that not all relationships are shown. Is that possible?

I'd need to check with @Joey or @Sam but I believe that's the application subscribed to GCP outage events and showing them in the UI. I'm not sure if it warrants impact to Authzed. Right now it's Google Cloud Compute Engine affected in all regions, but our monitoring does not show any impact on authzed.com When you say "not all relationships are shown" what do you mean?

I wrote a batch of new relationships. Only part of them can be seen in the Relationships table.

When I try to add them again, I get a message they already exist. So I guess it is a problem in the UI?

can you check via zed CLI? It could be an issue with UI yeah

WriteRelationships

operations are atomic, so it either fails as a whole, or succeeds as a whole

you can query

zed --help

and also each subcommand

sure, thanks 🙂

It seems that it is indeed a UI problem. Phew... 🙂

The UI only shows the first 50 rels of each type

Thanks for the info.

It’s not designed for showing everything

May be 25

I think it is 100. Thanks, I did not realize that.

maybe we can do a better job at clarifying that in the UI?

Are you sure? It seems to be possible to show multiple pages. If there is a limitation, you should show a prominent message.

It’s definitely limited to a maximum

I just forget how many off the top of my head

Then please add a message. I just asked my colleague and he was not aware either. 🙂

yep

I've created a very crude but usable standalone schema to json converter based on the work in this PoC: https://github.com/authzed/spicedb/pull/657 The goal was to get a list of definitions and the names of the relations and permissions so I could do some code generation. https://github.com/alsbury/spice2json

Any feedback is appreciated. I think that having support for some sort of annotation/attribute that you can put on relations and permissions would go a long way for adding metadata for applications that need to consume the schema.

Hello everyone, newbie here. I am researching on a rather crazy idea and wanted to get some expert thoughts to see if I have gone crazy. I am wondering if I can implement a licensing system on top of permissions. To me licenses are similar to permissions. E.g. in google folder - we can assign users + teams permissions to a root folder, then on subfolder I can override by adding/removing some permissions. Similarly I am wondering if a licensing system can work just like hierarchical folder structure. e.g. we have 100 customers. Customer1 is gives access to 50 seats + 5 admin users + 10k api usage limits + feature 1 Customer1 can create 2 teams Team 1 has 20 users + 1 admin user, 1k api usage limits but no feature 1 Team2 is special and gets 30 users + 1 admin user, 9k api usage limits and feature 1 access. Each team's admin user can further split into sub-teams if needed. When a user logs in, system will load all permissions the user has and accordingly enable/disable features. Is there a better way to do this? Has this been done with spicedb?

definitely doable and we have seen users defining feature flags as permissions before; a license if, as you state, just a set of permissions

for the numeric limits, you can likely use our newly released caveats feature