temporary_key_pair_name Applicability

[Lesley Kimmel]

I noticed that this SSH communicator option is available for several builders (based on the Packer docs). Specifically, I am using the vsphere-iso builder. I was playing with this option but it doesn't seem to do anything. When I search about it, it is generally in the context of Amazon builders. Is this option even applicable to the VMware builders? If so, how does it work?

[Rickard von Essen]

It's not applicable. It's just for builders where ssh public keys are served by the API to instances to that will be added by cloud-init (or something similar) will automatically add them to a authorized_keys file. 

On Thu, Apr 2, 2020, 04:15 Lesley Kimmel <lesley....@gmail.com> wrote:

I noticed that this SSH communicator option is available for several builders (based on the Packer docs). Specifically, I am using the vsphere-iso builder. I was playing with this option but it doesn't seem to do anything. When I search about it, it is generally in the context of Amazon builders. Is this option even applicable to the VMware builders? If so, how does it work?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/464b36a7-6d64-4227-86c0-4fb24c086e08%40googlegroups.com.

[Jason Beranek]

Rickard,

Probably worth a documentation update to capture the behavior/limitations.  I looked at the code, since I thought this was something that maybe used to work with the Virtualbox builders, and it looks like that code even generates the key pairs that it probably never uses.

V/r,

Jason A. Beranek

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.com.

[Rickard von Essen]

Actually this functionality has been extended a bit and it supports VirtualBox now at least. See https://packer.io/docs/builders/virtualbox-iso.html#ssh-key-pair-automation

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAE_nh6nSOkQ5EqAfdEVgjAvQc6khDtwD48Mva2amo-akHfEg2Q%40mail.gmail.com.

[Megan Marsh]

We are aware that the documentation is wrong here. Sorry :( The issue is that the docs are autogenerated, so they're showing up even for builders where specific options aren't relevant. We're working on fixing them so that builders which don't use certain communicator features won't show them as though they're available. 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt-7r%2BynA1dkLMkzYqbTzUYuEFy07CgLMoTiVGmB2EgN7g%40mail.gmail.com.

[Jason Beranek]

To be clear, I didn’t mean it as a criticism, and appreciate the plans to clean up the docs. I was thinking without considering the challenges of things being auto generated that cleaning up the docs could be a good starter task for external contributors. 

-Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAGPV1uqg_RuZ0O6vSP6JdQSMA41_PJHmSU2tmopjHwr3RPHdDw%40mail.gmail.com.