-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support context propagation on overloads #557
Comments
This is similar to what's exposed in #368; however, in that PR the There's been interest in reviving #368, so I'll take a look at what you're proposing and hopefully merge the approaches as best I can |
@TristonianJones Is this still on the agenda? We might be a bit out of line doing async calls as part of custom CEL functions, but this would simplify those use cases quite a bit (partly in terms of propagating request deadline, but also caller authentication for upstream RPCs!). |
@TristonianJones How can I help in adding this feature ? |
Feature request checklist
Change
Currently, it is possible to use go contexts with the
ContextEval(context.Context, interface{})
method. However, this context is not usable by function overloads.Example
The text was updated successfully, but these errors were encountered: