[jbosstools-issues] [JBoss JIRA] (JBIDE-12655) OpenShift Wizard should prevent the user from cloning if he did not uplod a public ssh key to OpenShift yet

[Isaac Rooskov (JIRA)]

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

Isaac Rooskov updated JBIDE-12655:
----------------------------------

    Release Notes Docs Status: Documented as Resolved Issue
                       Writer: irooskov
           Release Notes Text: Prior versions of OpenShift tooling created and uploaded public SSH keys to the OpenShift server when the user was creating the domain. This caused troubles when the user created the domain outside Eclipse (web console or command line) since the tooling was not prompting the user to upload keys to OpenShift. This has been corrected by now allowing SSH keys to be created and uploaded through a specific wizard. Furthermore the application wizard now errors if no keys are on the OpenShift server.  (was: Prior versions of OpenShift for JBoss Tools created and uploaded public SSH keys to OpenShift when the user was creating the domain. This caused troubles when the user created the domain outside Eclipse (web console or cli) since the tooling was not prompting the user to upload keys to OpenShift. Alpha2 now adds to create/upload SSH keys in a specific wizard. Furthermore the application wizard now errors if there are no keys on OpenShift yet. A link to the SSH keys wizard allows the user to create and upload those keys beforehand.)


Thanks so much for writing release note text Andre' :D I've altered it a little so it'll fit in for both JBT and the JBDS 6.0 release
                
> OpenShift Wizard should prevent the user from cloning if he did not uplod a public ssh key to OpenShift yet
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12655
>                 URL: https://issues.jboss.org/browse/JBIDE-12655
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>              Labels: new_and_noteworthy
>             Fix For: 4.0.0.Alpha2
>
>         Attachments: cloning-settings.png, no-keys.png, 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.
> How to reproduce:
> 1. ASSERT: make sure you have an OpenShift user without a domain (create a new user or kill your users domain)
> 2. EXEC: launch *OpenShift Application* wizard and create a new application
> Result:
> Cloning fails, since there are no ssh-keys on the local machine and no keys were added to OpenShift. The wizard did not tell the user since the domain already existed. The domain creation dialog is currently the only place that would allow a user to create a new ssh-key. If you already have a domain, you'll never get asked to create your keys.

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