[jbosstools-issues] [JBoss JIRA] (JBIDE-16401) OpenShift Explorer: Same connection as two different connections

[Michelle Murray (JIRA)]

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

Michelle Murray commented on JBIDE-16401:
-----------------------------------------

[~adietish], please can you provide me with some more info about express.conf.

My understanding is that this file is created when you use the OpenShift command line tool and run rhc setup, which itself uploads SSH keys etc.

Is this file ever created by OpenShift Tools? For example, what if I want to connect to my company's OpenShift Enterprise instance. I might want to have OpenShift Tools recognise that server as the default one when I make new connections. Where would I find the express.conf file to change the default server URL if I'm only using JBDS and OpenShift Tools? Does OpenShift Tools create an express.conf file the first time it connects to an OpenShift Enterprise or Origin instance just like it uploads SSH keys?
                
> OpenShift Explorer: Same connection as two different connections
> ----------------------------------------------------------------
>
>                 Key: JBIDE-16401
>                 URL: https://issues.jboss.org/browse/JBIDE-16401
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.1.Final
>            Reporter: Marián Labuda
>            Assignee: Andre Dietisheim
>            Priority: Minor
>
> It allows to have 2 "different" connections for one connection - 2 items in OpenShift Explorer view for same thing.
> Steps to reproduce:
> 1. EXEC: Open OpenShift explorer view
> 2. EXEC: Create connection to default OpenShift server with some credentials (checkbox for default server MUST BE checked)
> 3. ASSERT: Have connection in view with label "user server (default)"
> 4. EXEC: Open new connection shell (to create new connection)
> 5. EXEC: Uncheck checkbox for default server, but leave the same name and provide same credentials as in step 2.
> 6. EXEC: Confirm connection creation
> 7. ASSERT: There are now 2 "different" connections for same connection in OpenShift explorer view (e.g. "mlabuda at redhat.com openshift.redhat.com (default)" and "mlabuda at redhat.com openshift.redhat.com").
> Probably connections are distinguished by labels, I guess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira