Open rhopp opened 6 years ago
@l0rd do you know if there is an API for this?
There is no API exposed on wit side yet, but there is an issue[1] for it. Basically, It was planned to do stop / delete by communicating with che server directly as a first step - https://github.com/openshiftio/openshift.io/issues/1439#issuecomment-375609892
That's for @ashumilova and team/che/plugins
I'd recommend reclassifying this as type/feature-request
. Thoughts?
I agree.
ok, now that I have done that I'm having second thoughts. If the "delete" doesn't delete everything and leaves orphaned children that is a bad thing, right?
It's a "bad thing" but it's not a bug, because the specification never said "be sure to delete the workspaces." Defining "delete" broadly across OSIO is still an open item, and needs a lot of curation from PM, UXD and ENG.
Ultimately, this mainly a pain for the service, because it's wasting resources, but doesn't really impact users. We can probably do some scripted deletions if it becomes a large resourcing issue, until we have a more correct solution scoped and deployed.
Currently, when user removes codebase from codebases UI, all che workspaces created for this codebase are not deleted (orphaned ;-)). I think it would make sense to delete all workspace associated with the deleted codebase.