[ 
https://issues.apache.org/jira/browse/JCLOUDS-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007440#comment-15007440
 ] 

ASF subversion and git services commented on JCLOUDS-1033:
----------------------------------------------------------

Commit d91ea5f47f48f5550a5a26924f4f92ea1f0c1ffa in jclouds-labs's branch 
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=d91ea5f ]

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

Reply via email to