New event to represent a successful content decache #187
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
tonytw1
changed the title
JustinPinner
reviewed
Jan 6, 2021
| * the aliasPaths so that e.g. de-caching can be comprehensively | ||
| * triggered when the content is updated | ||
| */ | ||
| 4: optional list<string> aliasPaths |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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 does this change?
Introduces an event to represent Fastly CDN decaches.
Includes some basic meta data which the consume may find useful.
Intended as a lightweight substitute of the crier Event which can be iterated on to better suit the decached content use case.
How to test
How can we measure success?
Have we considered potential risks?
Images