You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently realized that the cache on Fastly is not purged when a new version of rustup is released.
rustup is distributed via static.rust-lang.org as part of the same Fastly services as the Rust releases. Ideally, we therefore only purge cached versions of rustup and don't purge the whole cache. We already do this for the Rust releases by setting surrogate keys that we can granularly purge.
Fastly's purge APIs require authentication. We can generate a token that is scoped to the service and only grants permissions to purge content. The token can be stored in the parameter store on AWS, similar to other tokens that we already use.
Tasks
Set a surrogate key for requests to /rustup/*
Create an authentication token for the release process and store it in SSM
We recently realized that the cache on Fastly is not purged when a new version of
rustup
is released.rustup
is distributed viastatic.rust-lang.org
as part of the same Fastly services as the Rust releases. Ideally, we therefore only purge cached versions ofrustup
and don't purge the whole cache. We already do this for the Rust releases by setting surrogate keys that we can granularly purge.Fastly's purge APIs require authentication. We can generate a token that is scoped to the service and only grants permissions to purge content. The token can be stored in the parameter store on AWS, similar to other tokens that we already use.
Tasks
/rustup/*
sync-dist.py
to purge the surrogate keyThe text was updated successfully, but these errors were encountered: