Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#369 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
php
Domaine
api, backend, database

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).

Langage dominant
PHP
Étoiles
40
Forks
72
Merge moyen
19 h
PR mergées (30 j)
66

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fleetbase/fleetops

Toutes les issues de fleetbase/fleetops

Issues similaires

Plus d'issues PHP

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.