Specifying existing private keys works only if keyfile name is the same as AWS keypair's

[utgarda]

Rudyfile:

role :stash do

      ami 'ami-55b39821'           # CentOS 5.4, 32bit

      users do

    root do

      keypair '/home/etsvigun/devenv/keys/etsvigun.pem'

    end

      end

    end

Output:

:~> rudy startup

 Executing routine: startup 

authorize port 22 access for: 194.186.67.200

  Rudy::PrivateKeyFileExists: Private key /home/etsvigun/devenv/keys/etsvigun.pem already exists.

(S)kip  (A)bort: s

  Rudy::AWS::Error: The key pair 'etsvigun.pem' does not exist

(S)kip  (A)bort: a

AWS adds '.pem' file extension automatically, thus default filename for a keypair is different from the keypair's name. If I rename the file and remove '.pem', works ok. Is it meant to be like that, or maybe I can specify both keypair and keyfile?

[delano]

You are correct, this is a limitation. I'll fix this in the next release.

Thanks for the detailed reports by the way!