[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=13447267#comment-13447267 ] 

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

The patch fixes what you described - changes to minishift home in server editor are persisted and visible as env vars in the launch config.
Now let's see if it actually works:
It starts ok, but then it fails to recognize the openshift user to use. So it will use openshift-dev which I believe is hardcoded in the tooling as a default - arguably the default should change to reflect openshift 3. But at least it helped me notice this :)
So it seems to me that when your tooling looks for the config file, it doesn't use the minishift home string.

> 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
>         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)