[jbosstools-issues] [JBoss JIRA] (JBIDE-25430) New Openshift Server should not allow editing connection

[Josef Kopriva (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josef Kopriva closed JBIDE-25430.
---------------------------------


Closing. Verified also with notes in PR.

Verified in:
Red Hat JBoss Developer Studio
Version: 11.2.0.AM3
Build id: AM3-v20171218-0506-B1798
Build date: 20171218-0506

> New Openshift Server should not allow editing connection
> --------------------------------------------------------
>
>                 Key: JBIDE-25430
>                 URL: https://issues.jboss.org/browse/JBIDE-25430
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, server
>    Affects Versions: 4.5.2.AM1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.5.2.AM2
>
>
> The openshift 3 new server wizard page allows you to change the details of the connection you've selected. This already seems very wrong. It's inappropriate for you to be changing the details of a connection that already exists, at least if you're not making a duplicate connection and leaving the original untouched.  
> Other server adapters or other parts of code may refer to these connections. Changing them in the new server wizard should not be a primary usecase. If the user does need to change them, it should be done via an 'edit connection' button, so teh user changes the connection but is aware he is changing it and is not simply making a duplicate with slightly different details. 
> Some of the fields (in the advanced section) are even changed on the connection EVEN if you CANCEL out of the new server wizard. THis is a big problem, and probably has more to do with the openshift connection API than anything. However, limiting that from occurring in the new server wizard will remove half the ways this bug can occur, so that's still a benefit. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)