[jbosstools-issues] [JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3
Rob Stryker (JIRA)
issues at jboss.org
Tue Sep 19 09:04:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465656#comment-13465656 ]
Rob Stryker commented on JBIDE-24236:
-------------------------------------
[~odockal]
1) New openshift connection / edit wizard has new widgets in the advanced section for the oc location to use with this connection.
2) This should be pre-filled with the workspace setting, if one exists, when creating an openshift connection
3) When JBDS starts up, and has an automatically created CDK, and user starts up a CDK, the oc location should be set to something like /home/rob/.minishift/cache/oc/v3.5.5.5/oc
> Preferences: "automagically" use the oc that's shipped with the cdk3
> --------------------------------------------------------------------
>
> Key: JBIDE-24236
> URL: https://issues.jboss.org/browse/JBIDE-24236
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: oc_binary, openshift_v3
> Fix For: 4.5.0.Final
>
>
> After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2
> Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it.
> Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list