Tag rustup artifacts with surrogate key #416
Merged
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
We use surrogate keys[^1] on Fastly to invalidate the cache for specific objects, e.g. when new versions of Rust or rustup are released. Surrogate keys are transparently set in the Fastly configuration based on the request path. A new VCL snippet has been added that tags every rustup artifact with the `rustup` surrogate key so that we can purge them from the cache when a new rustup version is released.
|
I wrote some documentation on how to test the surrogate keys here: rust-lang/infra-team#115 |
Mark-Simulacrum
approved these changes
May 17, 2024
16 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We use surrogate keys1 on Fastly to invalidate the cache for specific objects, e.g. when new versions of Rust or rustup are released. Surrogate keys are transparently set in the Fastly configuration based on the request path.
A new VCL snippet has been added that tags every rustup artifact with the
rustupsurrogate key so that we can purge them from the cache when a new rustup version is released.This is part of #415.
Footnotes
https://www.fastly.com/documentation/guides/concepts/edge-state/cache/purging/#surrogate-key-purge ↩