chore: further constraint RPC max message size #1222
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This sets stricter RPC message size limits on the OpenFGA gRPC server. Existing API definitions have strict limits on resource inputs and so the default 4MB gRPC message size limit is overly generous. Additionally, request
context
added for ABAC support is ultimately constrained by the RPC message size limit, and so setting a stricter limit on it is important to constrain the arbitrary request context that can be provided.I've also bumped up to the most recent protobuf API changes that were made in openfga/api#125
References
#1192
Review Checklist
main