[
https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-19178:
---------------------------------------
[~maxandersen] [~adietish] I attached a screen shot of an 'app' from the console
which is really a loose term. I believe we basically group things by the service and then
fill in some choice details from the other pieces based on how they match up via ports,
selectors, labels, etc. Given we don't have the freedom of html and are limited to a
tree, I would be interested in understanding how you think this would best be presented.
I'll try to sketch some idea.
Also, whats the easiest way to introduce the logical/pipeline view? Some right click
context 'switch' view (content provider) or a separate view all together. My
assumption is ultimately we would want to refactor the existing content provider so that
we dont have sync issues between various 'views' of all the same stuff
Explorer: Add "Pipeline" view to OpenShift v3 explorer
------------------------------------------------------
Key: JBIDE-19178
URL:
https://issues.jboss.org/browse/JBIDE-19178
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Alpha1
Reporter: Jeff Cantrill
Labels: explorer, openshift_v3
Fix For: 4.3.0.CR1
Attachments: Console of 'App' with the pieces wired.png
Add an alternate view in the openshift v3 explorer to try to 'link' resources in
a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)