Add Purge Front Door Cache action #87
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
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.
Inputs are strings: the name of the Front Door (e.g.
www-zooniverse-org) and the content path to purge (e.g./,/about/,/about/*, etc).This starts with support for a single string and requires multiple calls to purge multiple paths. However, it is possible to pass a string that can be processed into a matrix strategy (like
"'/', '/*'"or"'/', '/about', '/get-involved'"). I'm thinking that right now we might just process'/*'for the initial use case for this (post-FEM deploys) so I'll revisit if required.Also includes a test that purges the cache for https://frontend.preview.zooniverse.org/assets/star.jpg