The Rightscale inputs for the repo/repo_svn recipes imply that private key authentication is supported, but it isn't. If you specify a private key for the input, this is the kind of command that gets generated:
It would be great if the recipe supported private key authentication. At a minimum, the fact that it doesn't support it should be listed under known limitations so people know what to expect.
The Rightscale inputs for the repo/repo_svn recipes imply that private key authentication is supported, but it isn't. If you specify a private key for the input, this is the kind of command that gets generated:
The private key is being used with the --password option, but --password expects a password, not a private key. Private key authentication with subversion is generally done by setting up an IdentityFile in the user’s ~/.ssh/config ( http://stackoverflow.com/questions/192134/how-do-i-get-a-svn-checkout-using-a-public-private-key-pair ).
It would be great if the recipe supported private key authentication. At a minimum, the fact that it doesn't support it should be listed under known limitations so people know what to expect.