-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a job purging policy #70
Comments
I agree we should not keep eternally every Exports job, as many trainess are creating some that will not be sued anymore. Though there are some that are made to cover a specific location over a country (eg those you access when clicking on the markers on this umap: http://umap.openstreetmap.fr/en/map/central-african-republic_3868) and those could be maintained. Maybe create some superusers privileges for some people being able to tick a checkbox asking if the job should be maintained? |
for the second policy, I'm going to check if there are any new runs in the last 6 months, and if there are, the job would not be marked as 'deleted' |
Tasks:
|
cron job will execute at 01:00 every saturday |
period a job owner or an admin is able to toggle 'deleted' state, once the grace period ends, job, runs, and actual export data will be purged
toggle job 'deleted' state, effectively setting up execution of the first rule
The text was updated successfully, but these errors were encountered: