Actually it's not possible. The communicator hides this information and
also support a more sofisticated setup than just ssh user@host:port.
I recommend that you look at how the ansible (remote) provisioner tackles
this by running it's own ssh proxy. This required alot of implementation by
the
hi all! I'm building a new Packer provisioner plugin, and I need access to
the VM's SSH connection *settings* (I'm invoking a program that does SSH
itself). I can't however for the life figure out how to get to that info :(
Anybody an idea?
--
This mailing list is governed under the HashiCorp