e.g. if I have User A, with an edit relationship on Org A and Org B, and each Org has File A and File B respectively, I want to get only the records for Org A for which User A has access (i.e. ignore all records for which the user does not have access, and constrain the result to those related to Org A only)

generally you'd do a lookup and then check-filter it down further

or you'd check a different permission, but that's not dynamic

Hi folks, potential customer here. How on earth do I get hold of someone at authzed? I can't find an email on their website, and did not get any response from the schedule-call feature.

Can you DM me your details? You should have gotten a response from a form submission, or calendly is fully self-service

is there any documentation to build the spicedb from source code inside IDE?

to build SpiceDB itself?

yes please

go build .

in the

cmd/spicedb

directory will do so

we are going with license version but we are complex and large organisation so asked all sort of question like how comfortable our internal team is if it comes to self support.

there is also a Dockerfile in the repository that will build

thanks, so much ! will work on that !

Is there anyway to pass custom annotations to the

SpiceDBCluster

CRD when using the operator? I am trying to get access to the metrics on each instance and can do so with setting explicit annotations on the pods. I see in the docs (https://docs.authzed.com/spicedb/operator) there is an option for

extraPodLabels

but nothing about custom annotations. Submitted an issue here: https://github.com/authzed/spicedb-operator/issues/106

SpiceDB Operator | authzed

Does the authzed playground support: Caveated relationships?

Not yet! We are working on it. In the meantime you can see some example caveats here: https://github.com/authzed/spicedb/blob/052084677ceb476ff93f483a75098b762560d3fc/internal/dispatch/graph/computecheck_test.go

Okay, do you have any timeline in mind , when you plan to take it out of experimentation and mark it ready for production 🙂

We usually like to let these kinds of things play out a bit in the real world before taking them out of experimental

Should be before the end of the year though

related to the audit conversation: is there a way to look at two responses from (say) two WriteRelationships calls and determine the order in which they were applied to SpiceDB?

I'm unable to run

spicedb migrate head ...

successfully after upgrarding to 1.14. I get this error:

3:52PM INF configured logging async=false format=auto log_level=info provider=zerolog
3:52PM INF configured opentelemetry tracing endpoint= insecure=false provider=none service=spicedb v=0
3:52PM INF this is the latest released version of SpiceDB latest-released-version=v1.14.1
3:52PM INF migrating mysql datastore
3:52PM INF running migrations targetRevision=head
3:52PM INF migrating from= to=initial
3:52PM ERR datastore error error="sql: transaction has already been committed or rolled back"
3:52PM INF migrating from=initial to=add_unique_datastore_id
3:52PM ERR datastore error error="sql: transaction has already been committed or rolled back"
3:52PM INF migrating from=add_unique_datastore_id to=add_ns_config_id
3:53PM ERR datastore error error="sql: transaction has already been committed or rolled back"
3:53PM INF migrating from=add_ns_config_id to=add_caveat
3:53PM ERR terminated with errors error="unable to migrate to `head` revision: error executing migration `add_caveat`: statementBatch.execute: failed to exec statement: Error 1071: Specified key was too long; max key length is 767 bytes"

What is the collation set to for your database?

and are you using mysql <= 5.6?

The tables that are successfully created: "mysql_metadata" ---> latin1_swedish_ci "mysql_migration_version", "namespace_config", "relation_tuple" ---> utf8mb4_general_ci "relation_tuple_transaction" ---> no collation for any columns I'm using mysql 5.6.10

Can you upgrade to MySQL 5.7? 5.6 is EOL

I'm not sure, yet. Can 5.6 not work with 1.14?

Our min supported version is 5.7, and it would appear that you’re running into a known issue with index lengths on multi-byte collations in 5.6

ok, thank you.

Hi, just to make sure I did not miss something: It is not possible to follow a relationship in the opposite direction, right? So if I have a "parent" folder relationship, with "parent->editor" to inherit permissions from parent to child, it is not possible to use the relationship to inherit from child to parent, right? I need to create an additional "child" relationship to achieve that?

correct