[
https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi...
]
Jeff Cantrill edited comment on JBIDE-22241 at 6/1/16 10:46 AM:
----------------------------------------------------------------
I would defer this issue until
https://github.com/kubernetes/kubernetes/issues/19054
merges which will move cascade delete to the server instead of requiring us to duplicate
all the logic.
{{<kargakis> jcantril: for deploymentconfigs?
<kargakis> jcantril: or in general how to implement a reaper?
* rhcarvalho has quit (Remote host closed the connection)
* goern has quit (Quit: done for now)
<jcantril> kargakis, if i run 'oc delete <resource> cascade'...
* goern (~goern(a)aftr-37-201-171-241.unity-media.net) has joined
<jcantril> kargakis, we hope to provide similiar logic in the jbosstools openshift
tooling
<kargakis> jcantril: each reapable resource has to implement its own logic
* cdaley (~cdaley@2605:a000:160e:80c6:1202:b5ff:fe80:27c1) has joined
<kargakis> jcantril:
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/stop.go
* claytonc has quit (Read error: Connection reset by peer)
<kargakis> jcantril: all the upstream implementations
<jcantril> kargakis, does that mean then.... that cascade is a delete flag and the
api server interprets it accordingly?
* claytonc (~claytonc(a)75-130-183-34.static.hlrg.nc.charter.com) has joined
* ChanServ gives channel operator status to claytonc
<jcantril> kargakis, its just a flag to the request?
<kargakis> jcantril: oc delete can understand if <resource> is reapable or
not
<kargakis> jcantril: if <resource> is reapable, then the related reaper will
be used
<jcantril> kargakis, i dont wish to duplicate the reapable logic... just to
explicitly ask the cluster to cascade delete
<kargakis> jcantril: and all calls happen client-side
<kargakis> jcantril: cascade deletion is moving to the server upstream
* rhcarvalho (Rodolfo@nat/redhat/x-fcpoagpuinftkvls) has joined
<kargakis> jcantril: but it's still not there
* rlourenc has quit (Quit: Leaving)
* openshift-dev468 has quit (Quit: Page closed)
<jcantril> kargakis, so in order for me to cascade now....i would have to impl logic
that... for each kind ....reimpl what that particular type manages and delete those
resources
<kargakis> jcantril:
https://github.com/kubernetes/kubernetes/issues/19054
<kargakis> jcantril: yes, right now for each resource you would have to duplicate
the api calls that happen in oc}}
was (Author: jcantrill):
I would defer this issue until
https://github.com/kubernetes/kubernetes/issues/19054
merges which will move cascade delete to the server instead of requiring us to duplicate
all the logic.
OpenShift Explorer: Cascade resource deletion
---------------------------------------------
Key: JBIDE-22241
URL:
https://issues.jboss.org/browse/JBIDE-22241
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Marián Labuda
Assignee: Jeff MAURY
Labels: explorer, openshift_v3, ux
Fix For: 4.4.0.Alpha3
It would be nice to have a possibility to allow cascading deletion, deletion of related
resource/resource managed by the resource which is about to be deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)