Repository navigation
Fix the rotation comment: key limits follow the lineage - #116
Merged
Merged
Conversation
Rate-limit rules and budgets are attached to the key's lineage_id, which the rotated key keeps, so they carry over without a copy step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
The comment above key generation in
rotatesaid rate-limit rules and budgets are keyed by the key id and not copied on rotation. They are attached to the key'slineage_id(api_key_lineagesubjects), which the rotated key keeps, so they carry over. Comment only.🤖 Generated with Claude Code