844600078504951838 #spicedb

Channels

spicedb

test-forum

zanzibar

place

11/17/2022, 1:49 AM

no but i'll check it out. thanks!

Joey

11/17/2022, 1:56 AM

https://docs.authzed.com/guides/validation-and-testing for docs on it

place

11/17/2022, 2:20 AM

Another question; but is it possible for SpiceDB to distribute a full set of proto files? My org uses dotnet core which has great protobuf support via MSBuild. I couldn't find an easy way to download all the proto files + third-party proto files from buf's schema registry. I litterally had to copy/paste the file contents. It'd be really nice if there was a zip of all the needed protos in the github releases so that we can just download and start generating clients.

place

11/17/2022, 2:21 AM

I have seen this: https://github.com/jkulubya/authzed-dotnet but we really don't want to add buf into our workflow just to generate a spicedb client; and this repo doesn't actually publish a nuget package that we can reference.

place

11/17/2022, 2:22 AM

After downloading all the proto files (including google, openapiv2 and validate dependency protos) I can use MSBuild's protobuf support to generate a client

<Protobuf Include="./protos/**/*" AdditionalImportDirs="./protos" />

place

11/17/2022, 2:22 AM

was just a pain to get all the proto files because I had to hunt down the dep tree myself

Joey

11/17/2022, 2:27 AM

https://github.com/authzed/api/tree/main/authzed/api/v1

Joey

11/17/2022, 2:29 AM

that's the repo that pushes into buf

place

11/17/2022, 2:33 AM

Yeah but if you want to use protoc without buf you need to find the 3rd party protos yourself.

Protos
├── authzed
│   └── api
│       └── v1
│           ├── core.proto
│           ├── debug.proto
│           ├── error_reason.proto
│           ├── openapi.proto
│           ├── permission_service.proto
│           ├── schema_service.proto
│           └── watch_service.proto
├── google
│   └── api
│       ├── annotations.proto
│       └── http.proto
├── protoc-gen-openapiv2
│   └── options
│       ├── annotations.proto
│       └── openapiv2.proto
└── validate
    └── validate.proto

place

11/17/2022, 2:35 AM

I had to go to buf's schema registry site and download the content one by one. They dont have a download button so you have to copy/paste the text and create the correct folder structure yourself. If authzed added a zip into the github release that'd make it much simpler for non-buf user's to consume

Joey

11/17/2022, 2:47 AM

ah, yeah; it is indeed a bit harder to find them; might be worth asking Buf to add said button

Singha1

11/17/2022, 6:50 AM

What is this limitation? Can you show some light on that?

Joey

11/17/2022, 6:56 AM

MySQL 5.6 is now unsupported; we added a column that needs the larger index sizes in 5.7 - 5.6 has been EOL so it is officially unsupported everywhere

vroldanbet

11/17/2022, 8:29 AM

Please note MySQL 5.6 is also End-Of-Life as of early 2021.

ensonic

11/17/2022, 10:26 AM

Hi, went through the first_app tutorial both shell/go, running spiceDB in minikube on linux and bumped into https://github.com/authzed/zed/issues/169 on the check permission step - any ideas? I'll next try running the go check inside the cluster and I think this will address it, but would be nice to ensure the tutorial works

vroldanbet

11/17/2022, 10:31 AM

👋🏻 maybe I'm missing something but the tutorial does not indicate running in docker or in a kube-cluster. I think the tutorial assumes is spicedb gRPC port is exposed in the same network as zed. If you are using kube, you can do

kubectl port-forward

to the SpiceDB gRPC port locally

vroldanbet

11/17/2022, 10:34 AM

my apologies, I see you did in fact port-forward. Did you configure your

zed

context to run as

insecure

zed context set blog localhost:50051 my_token --insecure

vroldanbet

11/17/2022, 10:38 AM

if you run

zed context list

you can check if it's marked as insecure

ensonic

11/17/2022, 10:55 AM

yep, its is marked as insecure

ensonic

11/17/2022, 10:55 AM

all the other steps work

ensonic

11/17/2022, 10:56 AM

the only zed command that I found that fails is the one in the report

vroldanbet

11/17/2022, 11:01 AM

oh so other commands work? e.g.

zed schema read

? what version of

zed

and

spicedb

are you using?

ensonic

11/17/2022, 11:07 AM

zed version
client: zed 0.7.5
12:06PM WRN the version of SpiceDB being called is out of date. See: https://github.com/authzed/spicedb/releases/tag/v1.14.1 latest-released-version=v1.14.1 this-version=v1.11.0
service: v1.11.0

ensonic

11/17/2022, 11:07 AM

yep, the other commands work fine:

zed --skip-version-check schema read
definition blog/post {
    relation reader: blog/user
    relation writer: blog/user
    permission read = reader + writer
    permission write = writer
}

definition blog/user {}

vroldanbet

11/17/2022, 11:09 AM

weirddd. Would you mind adding this information to the issue? - versions - indicate that other zed commands work

ensonic

11/17/2022, 11:10 AM

done

ensonic

11/17/2022, 11:53 AM

ha, it tries to connect to a second port:

kubectl port-forward deployment/dev-spicedb 50051:50051
# in the example "localhost:50051"
go run check.go
2022/11/17 12:51:41 failed to check permission: rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing dial tcp 192.168.9.1:50053: connect: connection refused"

now notice the

192.168.9.1:50053:

seeruyy

11/17/2022, 2:52 PM

Based on this article is there some way to send a dispatch request through NodeJS client? https://authzed.com/blog/consistent-hash-load-balancing-grpc/

Joey

11/17/2022, 3:22 PM

its because its trying to dispatch to other nodes in the cluster

Joey

11/17/2022, 3:22 PM

port 50053 is the dispatch API