[
https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated WHIRR-641:
-------------------------------
Attachment: WHIRR-641.patch
This patch adds back in the (provider).image.login-user override if the
TemplateBuilderSpec in ClusterSpec returns non-null getLoginUser() - that gets
set to what, historically, has been spec.getBootstrapUser(). I've tested this
against our internal cloud setup, which happens to be that edge case where
passwords are hardcoded, and it didn't work without this patch...and it does
with it.
So the question is whether this is significant enough to merit a new RC. I'm
tending to think it isn't.
> 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