correct, but if you can help to test that works, then a PR should be easier.

I am not sure vagrant core developers use ansible to be able to test and
code that


Alvaro

On Tue, May 8, 2018 at 1:54 AM, pixel fairy <[email protected]> wrote:

>
>
> On Monday, May 7, 2018 at 12:39:42 AM UTC-7, Alvaro Miranda Aguilera wrote:
>>
>> not a chance you can test to deploy the certs that ansible can use with a
>> file provisioner or something?
>>
>> https://docs.ansible.com/ansible/2.5/user_guide/windows_
>> winrm.html#certificate
>>
>
> the point was to have the ansible provisioner handle these details in the
> background by default.
>
> its not that big a deal to throw an extra line in your playbook. just
> think vagrant should handle these things for the user.
>
>
>>
>>
>> Alvaro
>>
>> On Sun, May 6, 2018 at 3:24 AM, pixel fairy <[email protected]> wrote:
>>
>>> 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/ms
>>> gid/vagrant-up/be9be99c-3fff-45c2-a1c4-ce6afa3e4fb6%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/be9be99c-3fff-45c2-a1c4-ce6afa3e4fb6%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
> 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/fb35c13c-d704-455a-953d-bed349a93709%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/fb35c13c-d704-455a-953d-bed349a93709%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
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/CAHqq0eyhnjzze4kivSNyYO-N6rmwQGk_k8118PgtubU_UyV85Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to