CHEF-1928 / -i support in knife ssh screen/tmux


#1

Hi,

knife ssh screen/tmux ignores the -i argument, causing it to silently fail when
needed. Since it’s pretty common for EC2 clusters to not use personal keys but
a cluster-specific key, this could affect a decent number of folks.

I re-opened CHEF-1928 and refreshed the very small patch. It’s at

git://github.com/ivey/chef.git chef-1928_0.10

Any chance someone w/ commit can take a look? I keep having to manually patch
my gems every time I re-install.

Thanks!


#2

Hi,

On Tue, May 24, 2011 at 2:26 PM, ivey@gweezlebur.com wrote:

knife ssh screen/tmux ignores the -i argument, causing it to silently fail when
needed. Since it’s pretty common for EC2 clusters to not use personal keys but
a cluster-specific key, this could affect a decent number of folks.

I re-opened CHEF-1928 and refreshed the very small patch. It’s at

git://github.com/ivey/chef.git chef-1928_0.10

Any chance someone w/ commit can take a look? I keep having to manually patch
my gems every time I re-install.

This looks good to me. I will merge it tomorrow. Thanks for putting
together the patch and keeping track of the issue.

  • seth


Seth Falcon | Senior Software Design Engineer | Opscode | @sfalcon


#3

On Tue, May 24, 2011 at 5:45 PM, Seth Falcon seth@opscode.com wrote:

Hi,

On Tue, May 24, 2011 at 2:26 PM, ivey@gweezlebur.com wrote:

knife ssh screen/tmux ignores the -i argument, causing it to silently fail when
needed. Since it’s pretty common for EC2 clusters to not use personal keys but
a cluster-specific key, this could affect a decent number of folks.

I re-opened CHEF-1928 and refreshed the very small patch. It’s at

git://github.com/ivey/chef.git chef-1928_0.10

Any chance someone w/ commit can take a look? I keep having to manually patch
my gems every time I re-install.

This looks good to me. I will merge it tomorrow. Thanks for putting
together the patch and keeping track of the issue.

Merged to master.