[
https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi...
]
Hardy Ferentschik commented on JBIDE-20911:
-------------------------------------------
{quote}
not sure what you mean by virtual environment here ? the oc is supposed to be install on
users local host.
{quote}
I thought about the virtualized environment as provided by the Developer Platform. I guess
right now you indeed need the oc binary locally, because you cannot afaiu drive the
communication with the Openshift 3 instance purely via its REST API (due to the problems
with finding/implementing a Java client providing the required capabilities). If this
problem could be solved, it should be possible to do all "local" communication
via REST avoiding the need for the _oc_ cli altogether. If the user in such a case still
wants to use the _oc_ command line and has the virtualized environment of the Developer
Platform available, it should be possible to eg ssh to a virtual machine in this
environment which provides the _oc_ cli. Anyways, just a thought. I hope it is clearer now
what I meant.
open local terminal with oc already logged in
---------------------------------------------
Key: JBIDE-20911
URL:
https://issues.jboss.org/browse/JBIDE-20911
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Max Rydahl Andersen
it would be great to have a "Show in > OpenShift CLI" in openshift explorer
and on projects that are known to be on openshift that would use local terminal (like:
https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin>
--server=<serverurl>` executed at start.
This would allow users to work with CLI whenever the UI does not have exactly the command
needed by user.
* This assumes users have oc in their path
* might need different commands based on what OS (windows vs *nix)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)