disclaimer, all i know about winrm is that its kinda like windows equivalent to ssh if you squint at it just right from a far enough away.
windows doesnt work out of the box as expected with the ansible provisioner. theres two ways i think this can be fixed. 1. "ansible_winrm_server_cert_validation: ignore" in the generated inventory 2. dont ignore it, but use a self signed cert that vagrant already knows about, and have it generate a new cert the way it does with ssh. is option 2 possible? is it even worth the effort if windows is going to switch to ssh anyway? -- 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/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/be9be99c-3fff-45c2-a1c4-ce6afa3e4fb6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
