Closed chmouel closed 5 years ago
@chmouel Thinking of picking this up
how about
DELETE https://localhost:9091/api/metadataremoval/$namespace
what about /api/clear/metadata/${namespace}
?
@chmouel /api/clear/metadata/${namespace}
seems more appropriate
@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
hhmm, this would require authorization header as well as well, and then we won't need to pass namespace
parameter
sounds good 👍
Task list
curl -X DELETE http://localhost:9091/api/clear/metadata/ksagthi-preview-jenkins -H "Authorization: Bearer $SERVICE_ACCOUNT_TOKEN"
@sbose78 Can you verify if above is the expected API structure?
Provide an API which effectively do those SQL queries :
Find the jenkins namespace associated with the user - say ${user_jenkins_namespace}
https://openshift.io/openshiftio/Openshift_io/plan/detail/805