search

certat / do-portal

This project is in maintenance mode and will only receive bug fixes, but no new features. A new version of this software is being developed.
5 stars 5 forks source link

Garbage collector for stale RIPE Handle links #131

Open ghost opened 4 years ago

ghost commented 4 years ago

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 https://github.com/certat/do-portal/issues/83#issuecomment-645888142

ghost commented 4 years ago

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.

MarkHofstetter commented 4 years ago

I'll write a script that needs to be run after each import

do we have to inform user (which one?) and how?

certrik commented 4 years ago

All orga admins up the the hierarchy should be informed via email.

MarkHofstetter commented 4 years ago

f3357227c701e07d4990578780efa313ae83e316

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