[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14818:
----------------------------------------
Sprint: Sprint Beta2 CF
> Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_editor
> Fix For: 4.2.x
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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
12 years
[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-11408:
----------------------------------------
Sprint: Sprint Beta2 CF
> Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER)
> -----------------------------------------------------------------------
>
> Key: JBIDE-11408
> URL: https://issues.jboss.org/browse/JBIDE-11408
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift, upstream
> Environment: windows 7
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.x
>
>
> similar to https://issues.jboss.org/browse/JBIDE-10061
> When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error:
> git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/
> Cloning into 'kitchensink'...
> The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established.
> RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts.
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ WARNING: UNPROTECTED PRIVATE KEY FILE! @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open.
> It is required that your private key files are NOT accessible by others.
> This private key will be ignored.
> bad permissions: ignore key: /home/spousty/.ssh/id_rsa
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
> fatal: The remote end hung up unexpectedly
--
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
12 years
[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13096:
----------------------------------------
Sprint: Sprint Beta2 CF
> SSH key wizard: Add Existing SSH key: automatically provide sensible default-name
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-13096
> URL: https://issues.jboss.org/browse/JBIDE-13096
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: sshkeys_wizard
> Fix For: 4.2.x
>
>
> When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name.
> How to reproduce:
> # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer
> # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user
> # EXEC: in the upcoming dialog: hit "Add"
> Result:
> You get a dialog that asks you to browse and select your key and provide a name for it.
> Expected:
> Automatically provide some meaningful default name so that the newbie user may just pick his key and upload.
--
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
12 years
[JBoss JIRA] (JBIDE-13106) Tail files: Change icon and tooltip for "close console" to better show difference to closing view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13106:
----------------------------------------
Sprint: Sprint Beta2 CF
> Tail files: Change icon and tooltip for "close console" to better show difference to closing view
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13106
> URL: https://issues.jboss.org/browse/JBIDE-13106
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: different-close-actions.png
>
>
> The Server Log console has 2 distinct actions that are labeled "close console".
> !different-close-actions.png!
> 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation
> 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern.
> We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things.
--
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
12 years