Skip to content

de-duplicate CDN invalidations #2025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
syphar opened this issue Feb 4, 2023 · 1 comment
Closed

de-duplicate CDN invalidations #2025

syphar opened this issue Feb 4, 2023 · 1 comment

Comments

@syphar
Copy link
Member

syphar commented Feb 4, 2023

since #1961 we sometimes see a situation where multiple events related to a single crate lead to the same paths being queued for invalidation.

I saw this happening for example when:

  • a yank came shortly after a release
  • multiple releases were yanked

When the path invalidation is not yet sent to cloudfront, we can merge these entries.

@syphar syphar closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2023
@syphar
Copy link
Member Author

syphar commented Feb 4, 2023

I just realized the other issue (#1871) already includes this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant