This repository was archived by the owner on May 10, 2022. It is now read-only.
Add all invalidation types, implement key module #14
Conversation
This file contains hidden or 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
calvinbrewer
approved these changes
Aug 30, 2019
This was referenced Aug 30, 2019
|
Thanks! If you could tag a 0.0.7 release we can test this in our environment. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a big change. Master, currently only supports tag invalidation, which is by far the most important. Now I have support for all 8 invalidation types, although until I can figure out how to implement a custom invalidation type, regex will be used as a raw varnish ban expression type, because I figured that would be more useful.
These new invalidation types require a separate queuer than the default tag queuer, for example the drush module included with purge allows for queuing and processing invalidations of any type through the CLI.
The key module was implemented so that aperture passwords can be stored safely.