[jbosstools-issues] [JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450080#comment-13450080 ] 

Martin Malina commented on JBIDE-24796:
---------------------------------------

Now even the last remaining thing works correctly - the openshift user is correctly set - developer. And if I changed the user in the config file and then started cdk, the user used was changed accordingly, so that seems to work.
Verified in devstudio-11.1.0.AM1-v20170816-0706-B812-installer-standalone.jar .

> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24796
>                 URL: https://issues.jboss.org/browse/JBIDE-24796
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, openshift
>    Affects Versions: 4.5.0.Final
>         Environment: Fedora
>            Reporter: Ondrej Dockal
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.5.1.AM1
>
>         Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See 
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail! 
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
>  !cdk3_sa-manual_correct-mhome.png|thumbnail! 
> Cc: [~adietish] [~rob.stryker].



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)