Skip to content
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

Improve surrogate keys used for V3 endpoints #538

Open
notlee opened this issue Jul 23, 2021 · 1 comment
Open

Improve surrogate keys used for V3 endpoints #538

notlee opened this issue Jul 23, 2021 · 1 comment
Labels
feature New feature request service Relates to an Origami service
Projects

Comments

@notlee
Copy link
Contributor

notlee commented Jul 23, 2021

When we need to purge Fastly cache it can be difficult without purging everything, which we don't want to do.
So let's add surrogate key headers to allow us to purge bundles by:

  • language (js/css)
  • component (to purge all requests for a component)
  • component+version (to purge all requests for a specific component version)
@notlee notlee added the feature New feature request label Jul 23, 2021
@origamiserviceuser origamiserviceuser added this to incoming in Origami ✨ Jul 23, 2021
@github-actions github-actions bot added the service Relates to an Origami service label Jul 23, 2021
@notlee notlee changed the title Add surrogate keys to V3 bundle endpoints Improve surrogate keys used for V3 endpoints Jul 27, 2022
@notlee
Copy link
Contributor Author

notlee commented Jul 27, 2022

This PR adds surrogate keys to v3 endpoints. I'll leave this issue open as it could be improved by allowing us to purge all urls which contain a specific component or component+version. This would be super helpful in cases where users are including a component with a semver range ^ and we have deployed an important fix to a component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature request service Relates to an Origami service
Projects
Origami ✨
  
Backlog
Development

No branches or pull requests

1 participant