backend: account termination pipeline #47

Open
opened 2026-11-16 17:34:15 -05:00 by forgejo_admin · 0 comments
Owner

Reference docs/data-model.md, Account termination.

  • POST /admin/users/{id}/deletion, /admin/deletions, resolve (cancel / uphold)
  • mailer: notice email (en/es by user locale) with reason, date and appeal link; then sp_mark_deletion_notified; resend after an upheld appeal
  • POST /me/deletion-appeal
  • daily sp_execute_due_deletions and the stale-lease sweeper, each behind a DB lock (GET_LOCK) so one replica runs it
  • delete the executed users' now-orphaned objects through the blob collector

Conventions — CLAUDE.md and PLAN.md at the repo root.

Reference docs/data-model.md, Account termination. - [ ] `POST /admin/users/{id}/deletion`, `/admin/deletions`, resolve (cancel / uphold) - [ ] mailer: notice email (en/es by user locale) with reason, date and appeal link; then `sp_mark_deletion_notified`; resend after an upheld appeal - [ ] `POST /me/deletion-appeal` - [ ] daily `sp_execute_due_deletions` and the stale-lease sweeper, each behind a DB lock (`GET_LOCK`) so one replica runs it - [ ] delete the executed users' now-orphaned objects through the blob collector **Conventions** — CLAUDE.md and PLAN.md at the repo root.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#46 backend: admin API
k8s-services/dongba
Reference
k8s-services/dongba#47
No description provided.