Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Feature: an erase option for drivers (delete keeps personal data in the rows)

Aperta
  • Qualcosa non va?
#369 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php
Ambito
api, backend, database

Direzione di ricerca

Start by tracing DELETE /v1/drivers/{id} through ProfileAccountManager::releaseForProfile() and inspect how driver orders, activity rows, positions, and request logs are stored and referenced. The issue proposes several possible erase semantics but does not settle how to handle retained orders and proofs or request logs. Done would require an agreed erase behavior that removes personal data while preserving the specified delivery history and leaving staff accounts alone.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Is your feature request related to a problem? Please describe.

DELETE /v1/drivers/{id} soft-deletes the driver and, through ProfileAccountManager::releaseForProfile(), soft-deletes its managed user. Both rows keep the person's name, email, phone, username and last location. The update endpoint can't clear all of it first (username, for example), and activity rows and api_request_logs still hold the original contact details.

Deployments that must honor a deletion request (GDPR, CCPA, app store account deletion rules) have no API way to remove a driver's personal data.

Describe the solution you'd like

An erase option, for example DELETE /v1/drivers/{id}?erase=true or POST /v1/drivers/{id}/erase, that hard-deletes the driver and its managed login user (staff accounts left alone, as today), removes their activity rows and the driver's positions, and keeps orders and proofs, with the driver reference kept or pointed at a placeholder.

Separately, the soft delete sets driver_assigned_uuid to NULL on the driver's orders, including completed ones, so delivery history loses who made the delivery. That may be worth keeping.

Describe alternatives you've considered

Overwriting the fields with PUT before DELETE, which is what we do now. It leaves the username, activity rows and request logs behind.

Additional context

This would let Fleetbase be used for driver programs where deletion on request is a legal requirement. If you want it, we can send the PR. Fleetbase v0.7.68 (fleetops 0.6.71, core-api 1.6.68).

Lingua principale
PHP
Stelle
40
Fork
72
Merge medio
19h
PR unite (30g)
66

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fleetbase/fleetops

Tutte le issue di fleetbase/fleetops

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.