Garbage collector for stale RIPE Handle links
Opened this issue · 4 comments
if the handle is gone from the database an empty resposnse with status 204 is now returned
BUT we should consinder running a garbage collector after importing the ripe data which deletes the "stale" handles (and maybe inform the user about it)
Originally posted by @MarkHofstetter in #83 (comment)
BUT we should consinder running a garbage collector after importing the ripe data which deletes the "stale" handles (and maybe inform the user about it)
Yes, makes sense for me.
I'll write a script that needs to be run after each import
do we have to inform user (which one?) and how?
All orga admins up the the hierarchy should be informed via email.
to only list "stale" handles
python manage.py delete_stale_ripe_handles
3 ORG-TEST-RIPE 5
4 ORG-TEST2-RIPE 11
to actually delete stale handles
python manage.py delete_stale_ripe_handles --delete
3 ORG-TEST-RIPE 5
deleting
4 ORG-TEST2-RIPE 11
deleting
working on notification through the hierarchy