No way to enable SSH agent forwarding?

[mconigliaro]

No way to enable SSH agent forwarding?

[mconigliaro]

For future Googlers, the following ~/.ssh/config is apparently enough to make this work:

Host 127.0.0.1
  ForwardAgent yes

[mconigliaro]

Wait, this seems to be working for me anyway. Is it just enabled by default?

[pghalliday]

I don't think the workaround really fixes the underlying issue. The problem i have with that is that it's global and as such could hide problems in cookbooks where I do not want agent forwarding enabled (eg. if i'm creating keys on the machine). I still think there needs to be a way to specify whether to use agent forwarding on a case by case basis

[fnichol]

Currently SSH agent forwarding isn't directly supported, however you can supply your own custom Vagrant.erb template where you can enable agent forwarding or anything else for that matter. The driver uses a default Vagrantfile.erb which you could look to for ideas (although it's a bit crazy already to support everything existing).

[fnichol]

Whoops, forgot that this may be supported in Test Kitchen proper as of test-kitchen/test-kitchen@81e6112. If you set:

---
driver:
  name: vagrant
  forward_agent: true

then this should enable the feature when communicating with a Vagrant instance.

[pghalliday]

I did try forking and adding the forward agent as a parameter in the driver but then i realised that test kitchen doesn't use the vagrant provision or ssh interfaces to talk to the box - so it turned out to be pointless adding the option to the vagrantfile. I should then have looked at test kitchen itself i guess :)

thanks for the pointer!

[fnichol]

@pghalliday Ha, you're totally right about Vagrant, excellent point