You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/01/21 01:03:40 UTC
[jira] [Commented] (JCLOUDS-1033) DigitalOcean v2 should not fail
if no private key has been provided
[ https://issues.apache.org/jira/browse/JCLOUDS-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109777#comment-15109777 ]
ASF subversion and git services commented on JCLOUDS-1033:
----------------------------------------------------------
Commit 575d39e7c5c9974ecbe080a09a2787d08534ac3a in jclouds's branch refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=575d39e ]
JCLOUDS-1033: Don't fail if no private key has been provided in DigitalOcean
> DigitalOcean v2 should not fail if no private key has been provided
> -------------------------------------------------------------------
>
> Key: JCLOUDS-1033
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1033
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Affects Versions: 1.9.1
> Reporter: Ignasi Barrera
> Assignee: Ignasi Barrera
> Labels: digitalocean
> Fix For: 2.0.0
>
>
> The DigitalOcean v2 provider fails if there is no key pair auto-generation and the user does not provide a login private key. This might seem correct, but makes it impossible to use the ssh-agent to authenticate.
> The failure should be replaced by a warning message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)