Hello Rickard, thanks for your reply
On Mon, Aug 26, 2019 at 11:33 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:
> To get the IP for running ansible in shell-local do:
>
> A) Run a shell provisioner that saves the IP in a file. Use a file
> provisioner to download it and read it in the shell-local script.
>
How do I get the IP? I'm not aware of any packer variable or setting that
contains such value in a similar way as {{.WinRMPassword}} for password.
Or B) use some aws tag specific to this build and run the aws cli to find
> the IP of that instance.
>
That could be an option if option A does not work as expected.
>
> I would expect Ansible 2.8 with WinRM support in Packer to be at best
> rocky. But if you are into troubleshooting things it's probably worth at
> least trying.
>
Ansible 2.8 does work pretty well with WinRM. However, the special "packer"
connection used by ansible provisioner it requires a plugin, as far as I
know, but that's where I get confused.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/CAA3McK95gj%3D73d_grifK-GLCG8suhcVVQ9Pz5%3D0Kevj9-1ahmA%40mail.gmail.com.
