RE: [packer] quick chef provisioner query

Hi, Thanks so it looks like the defaults will do what I need. The only other question I have is the docs state that knife must be configured, how have people done this, I don’t really want to install the chef dk on each client system as some will be in production. Cheers Sean. From:

Re: [packer] Packer custom plugin: How to retrieve connection information?

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

RE: [packer] quick chef provisioner query

I will be running the chef job on production machines as they are brought in to production, and on machines when spun up for development locally. From: packer-tool@googlegroups.com [mailto:packer-tool@googlegroups.com] On Behalf Of Alvaro Miranda Aguilera Sent: 15 September 2016 22:46 To:

[packer] amazon-choot builder and CoreOS (newbie in Packer)

Quoting the docs "amazon-chroot - Create EBS-backed AMIs from an existing EC2 instance by mounting the root device and using a Chroot environment to provision that device. This is an advanced builder and should not be used by newcomers." It seems like you are not running your build from an

[packer] Packer custom plugin: How to retrieve connection information?

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