[12.x] Add Expired Flag to cache:clear #55642
Closed
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.
Overview
This PR adds the
--expired
flag to thecache:clear
artisan command. This is useful because expired cache items are not automatically deleted from the cache table once they have expired.The main thought behind adding this flag is that
cache:clear --expired
would be run on a set schedule (i.e. daily) inside ofroutes/console.php
.Usage
cache:clear --expired
will clean up any expired cache items for theDatabaseStore
only.--expired
flag is passed, only expired cache items will be removed from the cache table.cache:clear --expired
is run on a non-DatabaseStore
cache store, the command will run as if--expired
was not passed in the first place.Please let me know if you would like me to make any changes.
Note: An alternative option could be a dedicated command rather than changing behavior based on a flag. If desired, I can make those modifications in this PR.