[
https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-22241:
---------------------------------------
So that's how I am afraid it was meant ;) Simple delete could be probably more
sophisticated too. E.g. once you remove a service which had a routing, it makes almost no
sense to keep routing there. Because routing has mapping to a service so there would be
non-usable routing (unless you manually edit routing and point it to different service,
but who would do that and why?) Similar logic could apply to services - if selector in
service, usually deployment config, does not exists and neither replication controller, it
does not make much sense to keep service alive.
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.1.Alpha1
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)