Fix key rotation #160
Merged
Fix key rotation #160
Conversation
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
aram356
requested changes
Jan 22, 2026
Collaborator
aram356
left a comment
aram356
left a comment
There was a problem hiding this comment.
👍 Looks good overall. I added small nitpicks to address.
aram356
approved these changes
Jan 26, 2026
ChristianPavilonis
force-pushed
the
fix/key-rotation
branch
from
90f7f58 to
5aea994
Compare
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.
Previously using hardcoded backend names, we later added port number to the dynamic backend names which broke the key rotation.
Now the fastly client will use the generated backend name.
closes #185