search

fabric8-services / fabric8-jenkins-proxy

Apache License 2.0
1 stars 16 forks source link

API for metadata removal: GDPR compliance #322

Closed chmouel closed 5 years ago

chmouel commented 6 years ago

Provide an API which effectively do those SQL queries :

Find the jenkins namespace associated with the user - say ${user_jenkins_namespace}

DELETE FROM statistics WHERE namespace = '${user_jenkins_namespace}';
DELETE FROM requests WHERE namespace = '${user_jenkins_namespace}';

https://openshift.io/openshiftio/Openshift_io/plan/detail/805

kishansagathiya commented 5 years ago

@chmouel Thinking of picking this up how about DELETE https://localhost:9091/api/metadataremoval/$namespace

chmouel commented 5 years ago

what about /api/clear/metadata/${namespace} ?

kishansagathiya commented 5 years ago

@chmouel /api/clear/metadata/${namespace} seems more appropriate

kishansagathiya commented 5 years ago

@chmouel I see a function to soft delete requests. I can't imagine why we would need this info in future(except for doing some analytics). I am inclined towards not keeping separate soft-delete and hard-delete function, and just hard-delete them both. Let me know if you think I should keep soft-delete

Don't see deleted_at column

kishansagathiya commented 5 years ago

hhmm, this would require authorization header as well as well, and then we won't need to pass namespace parameter

chmouel commented 5 years ago

sounds good 👍

kishansagathiya commented 5 years ago

Task list