Skip to content

CTF-704: Event Force Delete

Statement

The system should support force-deleting an event and all associated resources regardless of event state. Force delete shall cascade to: all range instances (destroyed immediately), all participant registrations, all challenge data, all submissions and scores, and all scheduled tasks. Force delete shall require explicit confirmation including typing the event name. The action shall be logged with the actor and timestamp.

Rationale

Force delete is the nuclear option for events that need to be completely removed, failed test events, cancelled events with provisioned resources, or events created in error. Without force delete, organizers must manually clean up each resource type, and orphaned ranges continue accruing costs.

Traceability

  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/services/event/ (delete_event() - soft-delete only, no force-delete or cascade logic)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/services/event/ (force_delete_event() - service function for force-deleting events with cascade)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/views/ (Admin view and API endpoint for force-deleting events)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/urls.py (URL patterns for force-delete admin view and API endpoint)