[jbosstools-issues] [JBoss JIRA] (JBIDE-12016) OpenShift Wizard - SSH2 Preferences

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-12016:
---------------------------------------------

And Burr - we got info message saying the key should be added to preferences with a link to the preferences where you can create keys etc.
What other kind of warning do you want to add that is not super annoying to have?

Its only recently openshift separated the key from the creation time which explains why we only have ssh key upload when creating the domain.

And if there already is a key, why would you want to delete the poorly created apps ? those apps works fine when you have the old or add a new key.

And SSH is only a nightmare if you actually don't use JBDS to create your app with it.

We can't get this in before codefreeze (a few hours), thus recommendation is: Create your openshift account online, use JBDS to set everything else up.





                
> OpenShift Wizard - SSH2 Preferences
> -----------------------------------
>
>                 Key: JBIDE-12016
>                 URL: https://issues.jboss.org/browse/JBIDE-12016
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Burr Sutter
>            Assignee: Andre Dietisheim
>             Fix For: 3.4.x
>
>         Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift.
> At least 10 users failed this test today and had to be "handheld" through the process.   
> What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again.
> The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class.  SSH is still a nightmare for the newbie trying to use OpenShift + JBDS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira