Add new command to clean old log entries, fixes issue #622 #623
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 are you changing/introducing
Adding new console command implementing the log cleaning feature
This new command will do it (via a cron job on a monthly bases for instance) where it will delete log files older than YYY years but only if we have more more then XXX rows. This ensures log files won’t be deleted if there just a few log entries.
What is the reason for changing/introducing
Overtime log tables such as admin_ngrest_log and cms_log will contain large amount of data. To keep the database cleaner and if we don not need these logs anymore we have to manually perform a cleanup.
QA