Repository navigation
feat: add limit_by_ip to rate limit resources - #17
Merged
Merged
Conversation
luccastera
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
limit_by_iptoquicknode_endpoint_rate_limitsandquicknode_endpoint_method_rate_limit, matching the "Limit by IP address" option in the dashboard.quicknode_endpoint_rate_limits: optional. Left out of the configuration, it keeps the endpoint's current value. Destroying the resource turns it off.quicknode_endpoint_method_rate_limit: optional, defaults tofalse.Also regenerates the Admin API client from the current published spec, and updates docs, examples and the changelog.
Closes #13