Add option to rate limit the publish endpoint #1420
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.
This adds an option to rate-limit the publish endpoint. By default it will use a memory one with lru-cache, but it's extendable by passing an object that follows the interface described so you could plug-in Redis or whatever library you want. I'm leaning towards enabling this by default
Rate Limiting
The registry supports rate limiting for the publish endpoint to prevent abuse. By default, it allows 100 requests per 15 minutes per IP/user combination.
Basic Configuration
Advanced Configuration
Custom Storage Backends
You can implement custom storage backends by creating a class that implements the
RateLimitStore
interface: