Skip to content

Conversation

@efd6
Copy link
Collaborator

@efd6 efd6 commented Sep 10, 2025

Previously, the application of rate limits was left entirely to the host code after the CEL program evaluation has completed. This leaves the possibility for a collection of work items to deplete the rate limiter's token bucket in the middle of a CEL program evaluation. This change adds the possibility of adding a hook for application of rate limit values on completion of a call to rate_limit, allowing more fine rate limits to be respected more dynamically.

Please take a look.

Previously, the application of rate limits was left entirely to the host
code after the CEL program evaluation has completed. This leaves the
possibility for a collection of work items to deplete the rate
limiter's token bucket in the middle of a CEL program evaluation. This
change adds the possibility of adding a hook for application of rate
limit values on completion of a call to rate_limit, allowing more fine
rate limits to be respected more dynamically.
@efd6 efd6 self-assigned this Sep 10, 2025
@efd6 efd6 marked this pull request as ready for review September 10, 2025 00:20
@efd6 efd6 requested review from a team and andrewkroh September 12, 2025 07:38
@efd6 efd6 merged commit a11417a into dev Oct 6, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants