User story #2973
Updated by François ARMAND over 11 years ago
In Rudder 2.5, we want to provide a UI to configure job frequency of report cleaning, see #2971.
But the bug is so impacting for our user that we want to try to implement a simplified version for Rudder 2.4, based on #2972 and a textfile-based configuration.
Properties of the text file will be:
- age (in days) before archiving report
- age (in days) before deleting report
- an age of 0 (or less) means "no automatic cleaning"
- frequency of the job:
- hourly + minutes when the job is executed,
- daily + hours/minutes when the job is executed,
- weekly + name of the day/hours/minutes when the job is executed.
Add in the DB management page a message: "Automatic cleaning execution can be configured thanks to parameters ... of config file."
(Even better: "Current parameters: ...")
We also have to add new event logs for automatically executed cleaning.
As for #2972, the final acceptance in Rudder 2.4 is subject to the quantity/impact of code needed to add that feature.