feat: Purge cache for specific objects #650
Merged
Conversation
This file contains 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
⛔ Snyk checks have failed. 2 issues have been found so far.
⛔ code/snyk check is complete. 2 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![snyk-io[bot]](https://avatars.githubusercontent.com/in/372950?s=60&v=4){kind=small}
fenos
force-pushed
the
feat/purge-cache-for-object
branch
4 times, most recently
from
15c42e0 to
2c01e2c
Compare
Pull Request Test Coverage Report for Build 14262662188Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 14218413363Details
💛 - Coveralls |
itslenny
approved these changes
Apr 2, 2025
fenos
force-pushed
the
feat/purge-cache-for-object
branch
3 times, most recently
from
e0f8d9d to
a03cfaa
Compare
fenos
force-pushed
the
feat/purge-cache-for-object
branch
from
a03cfaa to
1a32426
Compare
|
🎉 This PR is included in version 1.20.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
What kind of change does this PR introduce?
Feature
What is the current behavior?
Currently is not possible to purge the cache programmatically
What is the new behavior?
This PR introduces a new endpoint:
DELETE /cdn/{bucket}/{object}that allows purging the cache for a specific objectAdditional context
The actual implementation for purging the cache sits outside of storage, this is because we don't want to couple the service
to a specific purge mechanism.
Storage invokes an external HTTP endpoint, which does the purging to keep it agnostic