[
https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-22243:
---------------------------------------
At the moment refreshing of a service and pod does nothing. This is related also to
OpenShift Explorer view. Refreshing of projects and connections works fine.
I am not sure whether having a Refresh context menu item on a pod is reasonable (mostly
bcs. refresh on the pod tree item should refresh the item itself and also underlying tree
items, what does not make sense in this case imho. Pods of any kind (builds, application,
deployment) are volatile - changing anything higher in hierarchy (e.g. environment
variable, changing config etc) respin a pod and its already different item...).
Refresh on a service do nothing. I have not spotted any running job there, not underlying
tree items are not refreshed. One outstanding question, again, is whether it is worth of
having a Refresh for a service (if watcher would fail it would be nice, but we should
ensure watcher is working all the time, if it is bugged, fix it so we would not have to
worry about it). Also refreshing of a service to gets only its underlying pods, is this
even possible without refreshing also other services lying under the same project?
Properties: "Refresh" has no effect
-----------------------------------
Key: JBIDE-22243
URL:
https://issues.jboss.org/browse/JBIDE-22243
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Jeff Cantrill
Fix For: 4.4.0.Alpha2
Attachments: refreshing-wont-help.ogv
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)