Whirr
  1. Whirr
  2. WHIRR-641

No longer possible to hardcode password for bootstrap user

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.8.1, 0.9.0
    • Component/s: core
    • Labels:
      None

      Description

      (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.

      1. WHIRR-641-pt2.patch
        1 kB
        Andrew Bayer
      2. WHIRR-641.patch
        19 kB
        Adrian Cole
      3. WHIRR-641.patch
        0.8 kB
        Andrew Bayer

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Adrian Cole (Inactive)
            Reporter:
            Andrew Bayer
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development