OpenFGA v0.3.6
is out with improved tracing, a grpc health probe and fixes to Check
and ListObjects
#113
Replies: 2 comments 29 replies
-
Thanks ❤️. Btw, It's |
Beta Was this translation helpful? Give feedback.
-
Urgent: ListObjects endpoint not working in new update. Possible causes; v0.3.6 OPENFGA_LIST_OBJECTS_DEADLINE - It may not see or detect the set time. OPENFGA_HTTP_UPSTREAM_TIMEOUT - It may not see or detect the set time. |
Beta Was this translation helpful? Give feedback.
-
Hey folks!
We just released OpenFGA
v0.3.6
. It is a re-release ofv0.3.5
due to some release pipeline issues with the previous release.v0.3.6
comes with improved support for telemetry & tracing and a grpc health probe and fixes toCheck
andListObjects
.If you are running through docker:
docker pull openfga/openfga
openfga/openfga:v0.3.6
Changes in this release
Added
grpc-health-probe
for Health Checks (#520)OpenFGA containers now include an embedded
grpc_health_probe
binary that can be used to probe the Health Check endpoints of OpenFGA servers. Take a look at the docker-compose.yaml file for an example.Improvements to telemetry: logging, tracing, and metrics (#468, #514, #517, #522)
We have added Prometheus as the standard metrics provided for OpenFGA and provide a way to launch Grafana to view the metrics locally. See docker-compose.yaml for more information.
We've improved the attributes of various trace spans and made sure that trace span names align with the functions they decorate.
Our logging has been enhanced with more logged fields including request level logging which includes a
request_id
andstore_id
field in the log message.These features will allow operators of OpenFGA to improve their monitoring and observability processes.
* Nightly releases (openfga/openfga#508) - thanks @Siddhant-K-code!You should now be able to run nightly releases of OpenFGA usingdocker pull openfga/openfga:nightly
(Note: Nightly releases are having some issues with our pipeline, we'll announce when that's fixed)
Fixed
Undefined computed relations on tuplesets now behave properly (#532)
If you had a model involving two different computed relations on the same tupleset, then it's possible you may have received an internal server error if one of the computed relations was undefined. For example,
Given the tuple
{ user: "org:contoso", relation: "parent", object: "document:1" }
, thenCheck({ user: "jon", relation: "viewer", object: "document:1" })
would return an error prior to this fix because thex
computed relation on thedocument#parent
tupleset relation is not defined for theorg
object type.Eliminate duplicate objects in ListObjects response (#528)
Beta Was this translation helpful? Give feedback.
All reactions