update: add Gitlab deletion host and task for user deletion requests
- update: add Gitlab deletion host and task for user deletion requests
To handle full GDPR, users should be hard removed from GL systems rather than kept around after the normal user deletion. While the account would be inaccessible, the name and account would be active. This could lead to additional notifications from a should-be deleted service as well as their name not being fully forgotten.
Resolves infrazilla#2001
Merge request reports
Activity
added 1 commit
- f1f23e90 - update: add Gitlab deletion host and task for user deletion requests
@cguindon I've used a "hard delete" here as it would remove references to the name, which is a more full "forgetting" experience. Let me know if we should retain the username for records instead!
In the spirit of collaboration and transparency, I believe contributions should be assigned to ghost users. This aligns with the approach we've taken on many of our collaborative platforms, such as our wiki and forums.
A hard delete would only be appropriate for spammers or users who haven’t contributed anything meaningful.
//FYI @mward
added 1 commit
- ae8f23f2 - fix: remove hard delete, as it is too eager in deletion of contributions
added 1 commit
- e59f6302 - update: fix comments to remove references to hard deletes
requested review from @malowe
requested review from @heurtemattes and removed review request for @malowe
added 1 commit
- d37e24f2 - update: add ability to disable GL deletion while keeping task active
added 11 commits
-
d37e24f2...8bf9d905 - 7 commits from branch
main - 0bb01670 - update: add Gitlab deletion host and task for user deletion requests
- 1a9d503c - fix: remove hard delete, as it is too eager in deletion of contributions
- d3797583 - update: fix comments to remove references to hard deletes
- eb79ccb5 - update: add ability to disable GL deletion while keeping task active
Toggle commit list-
d37e24f2...8bf9d905 - 7 commits from branch
requested review from @gnugomez
30 import org.slf4j.LoggerFactory; 31 32 import io.quarkus.scheduler.Scheduled; 33 import jakarta.inject.Inject; 34 import jakarta.ws.rs.WebApplicationException; 35 import jakarta.ws.rs.core.MultivaluedHashMap; 36 import jakarta.ws.rs.core.MultivaluedMap; 37 import jakarta.ws.rs.core.Response.Status; 38 39 /** 40 * Actions GitLab user deletion request records. 41 */ 42 public class GitlabUserDeletionTask { 43 private static final Logger LOGGER = LoggerFactory.getLogger(GitlabUserDeletionTask.class); 44 45 @ConfigProperty(name = "eclipse.profile.scheduled.gitlab-deletion.enabled", defaultValue = "true") changed this line in version 7 of the diff
added 1 commit
- 6e04c8da - feat: Update GitLab deletion to better extract logic to related services
