define and implement Okapi tenant clean up operation
Description
Environment
None
Potential Workaround
None
relates to
Checklist
hideTestRail: Results
Activity
Show:
shale99 June 18, 2018 at 9:57 AM
that is how it is implemented in RMB modules - sending a DELETE to /_/tenant willl remove the db user for the tenant as well as erase the schema (including data) - anything else that is needed can be extended by a module developer
Jakub Skoczen June 18, 2018 at 9:54 AM
Are you saying that the existing DELETE /_/tenant is used for purge rather than disable?
shale99 June 18, 2018 at 9:50 AM
right now the DELETE /_/tenant is a purge, we need a new purge
Jakub Skoczen June 18, 2018 at 9:47 AMEdited
Yes, of course it should be /_/tenant. Fixed in my comment. The idea here is that the tenant remains the "resource" (in restful terms) and we are mapping operations on top of HTTP methods.
shale99 June 18, 2018 at 9:45 AM
for the purge? i think so, yes
Done
Created May 30, 2018 at 2:11 PM
Updated August 8, 2018 at 1:22 PM
Resolved June 12, 2018 at 1:02 PM
TestRail: Cases
TestRail: Runs
We need two operations for a module in the tenant interface:
deactivate – this should allow to deallocate any temporary resources like open DB connections
purge – this should allow to destroy any persistent tenant data and configuration
The "deactive" operation should be called on a module automatically during tenant removal from Okapi.
Purge is part of OKAPI-609