I am looking into using keto for our app, and i wa...
# talk-keto
v
I am looking into using keto for our app, and i was wondering what
alpha
in the release name means for me, is it not production ready or does it just mean that there might be breaking changes down the road?
s
tl;dr just breaking changes
we obviously try to keep changes at a minimum, but are not yet confident that we can guarantee that
v
thank you very much!!
is there any timeline on when it's going to be in the Incubating state?
s
no not really, but we are recently putting a lot of effort into moving Keto forward
v
thats great! btw the multiple endpoints for
relation-tuples/check
(the second with
openapi
at the end, all of them as
post
and
get
) is confusing. even if they are all needed - in the documentation its not really clear why they are there, they all have the same description...
talking about this - there's four of them
s
agree, would also prefer to not have all of those... but we need the openapi variants because the generated clients typically fail/through on non-2XX status codes on the other hand, some API gateways only look at the status code and want that to contain whether an action should be allowed
v
got it.
could it be added the the description maybe?
s
sure, would you be up for that contribution? it is just a matter of updating these comments: https://github.com/ory/keto/blob/de164ac92aa0fa6e22257530fc48adb6857d7fff/internal/check/handler.go#L83-L100
v
i'd be happy to
what about the get/post?
s
often path and query params are leaked to logs, having the stuff in the body typically makes it not show up
but it is really a get operation, not a post one...
v
what do the other Ory projects do?
s
regarding to what?
v
regarding path and query params often being logged
s
they typically only have the id in the URL
which would be fine, but is not possible in keto