spicedb
- t
tarrooon
07/31/2021, 12:52 PMGreat talk. Definitely learnt a lot! 🙂 Would love to see Authzed implementation on GitHub in the near future! - u
user
08/02/2021, 8:43 PMThanks! We've all worked at open source companies (CoreOS, Red Hat), so we are definitely keeping an eye to where it makes sense to open source. - a
Arash
08/16/2021, 2:20 AMHi folks. I just signed up with authzed to investigate it for a client project, but when I log in, I see an infinite loading screen: - a
Arash
08/16/2021, 2:23 AMI figured it out. Looks like I need to verify my email before logging in. A dialog there would be helpful after creating your account. 🙂 - j
Joey
08/16/2021, 4:02 AM@User thanks for the bug report. We'll get it sorted ASAP. What login did you use to sign in? - a
Arash
08/16/2021, 4:44 AMGot another bug report for you. I found a broken link pointing to https://docs.authzed.com/mgmt/organizations - j
Joey
08/16/2021, 5:22 AMYeah, we actually noticed it Friday; the change hasn’t been deployed yet - j
Joey
08/16/2021, 5:22 AMthanks - u
user
08/16/2021, 2:52 PMThanks for the reports @User -- we just enabled user & password logins so I'm sure we have a few small issues. - u
user
08/18/2021, 5:25 PM@here Hey everyone! We just open-sourced the proxy that we use to secure our monitoring stack: you can read about it here https://authzed.com/blog/prom-authzed-proxy/ and check out the code here https://github.com/authzed/prom-authzed-proxy - u
user
08/26/2021, 2:45 AMhmm... does anybody know if there are popular integrations that we could use to get github events streamed into discord? - b
Ben RMX
08/26/2021, 3:38 PMtrying out the zed cli, just brew tap installed this morning.
returns an error with messagezed relationship delete btwb_development/document:firstdoc reader btwb_development/user:fred
the cli usage saysError: rpc error: code = InvalidArgument desc = invalid WriteRequest.Updates[0]: embedded message failed validation | caused by: invalid RelationTupleUpdate.Tuple: embedded message failed validation | caused by: invalid RelationTuple.ObjectAndRelation: embedded message failed validation | caused by: invalid ObjectAndRelation.Namespace: value does not match regex pattern "^([a-z][a-z0-9_]{2,62}[a-z0-9]/)?[a-z][a-z0-9_]{2,62}[a-z0-9]$"
but that regex doesn't include the colonUsage: zed relationship delete <subject:id> <relation> <object:id> [flags]
?: - u
user
08/26/2021, 3:43 PMhey there, have you tried without the namespace? - u
user
08/26/2021, 3:43 PMthe zed login context has the namespace so you should be able to do - u
user
08/26/2021, 3:43 PMzed relationship delete document:firstdoc reader user:fred - u
user
08/26/2021, 3:44 PMit's probably sending
to the serverbtwb_development/btwb_development/document:firstdoc - b
Ben RMX
08/26/2021, 4:15 PMthanks. that was it... what i had to do: 1. remove the namespace 2. and also reverse that subject objectzed relationship delete user:fred reader document:firstdoc - u
user
08/26/2021, 4:24 PMif you don't mind, you could create an issue on zed to handle the case where the user actually passes the namespace on the CLI - u
user
08/26/2021, 4:24 PMotherwise, i'll make it - u
user
08/26/2021, 4:25 PMthanks for trying out zed btw -- it makes it easier for us to sus out ux friction like this - b
Ben RMX
08/26/2021, 4:27 PMcreated a quick issue: https://github.com/authzed/zed/issues/19 - u
user
08/26/2021, 4:27 PMthanks! - b
Ben RMX
08/26/2021, 4:28 PM👍 yeah, the subject-relation-object vs object-relation-subject difference got me a few times in the playground - u
user
08/26/2021, 4:28 PMyeah, it's tricky because the playground relies on it to provide autocomplete - u
user
08/26/2021, 4:29 PMbut outside of the playground i think most people think of it as "SVO" - u
user
08/26/2021, 4:29 PMsince, well, english works that way - b
Ben RMX
08/26/2021, 4:30 PM👍 - b
Ben RMX
08/26/2021, 4:34 PManother question, and is this an issue to create in one of the authzed repos? When I change the schema in the playground and re-import into the permission system, I see the notice that it will keep the old definitions around. Are there plans to enable/allow admins of the schema/permissionSystem to remove such definitions (and any relation to it)?