Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easier ssh keypair naming #93

Closed
wants to merge 1 commit into from
Closed

Conversation

pcn
Copy link

@pcn pcn commented Jan 10, 2012

  • Checks for ssh_identity_dir/<keypair>_rsa
  • Checks for ssh_identity_dir/<keypair>
  • Checks for ssh_identity_dir/id_<keypair>
  • falls back on ssh_identity_dir/<keypair>.pem

cloud.ssh_identity_dir needs to be set to ~/.ssh to work properly, otherwise
strange things happen in ~/.chef/ec2_keys.

This is all to allow for an AWS keypair name in ec2 to be e.g. "staging" and the
associated file be "/.ssh/id_staging" or "/.ssh/staging_rsa".

- Checks for ssh_identity_dir/<keypair>_rsa
- Checks for ssh_identity_dir/<keypair>
- Checks for ssh_identity_dir/id_<keypair>
- falls back on ssh_identity_dir/<keypair>.pem

cloud.ssh_identity_dir needs to be set to ~/.ssh to work properly, otherwise
strange things happen in ~/.chef/ec2_keys.

This is all to allow for an AWS keypair name in ec2 to be e.g. "staging" and the
associated file be "~/.ssh/id_staging" or "~/.ssh/staging.rsa".
@temujin9
Copy link
Contributor

We have a similar feature need on the cleanup list for version 3, which would collide with this code. Closing this, but we'll keep an eye on your requirements while developing that.

@temujin9 temujin9 closed this Feb 21, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants