[jira] [Commented] (WHIRR-641) No longer possible to hardcode password for bootstrap user

["Adrian Cole (JIRA)" <ji...@apache.org>]

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

Adrian Cole commented on WHIRR-641:
-----------------------------------

like so many things in whirr.  this issue smells of many missing test cases.
                
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
>                 Key: WHIRR-641
>                 URL: https://issues.apache.org/jira/browse/WHIRR-641
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>            Priority: Critical
>             Fix For: 0.9.0
>
>         Attachments: WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.

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