yep, lets' hope he cooks up something :-) Its a bit of a pita atm.
On Wednesday, April 26, 2017 at 10:17:27 AM UTC+2, Jordan Borean wrote:
>
> 2.3 removed this unfortunately with the way the execution wrapper now
> works. I believe Matt was looking at reverting the behavior to what it was
> befo
2.3 removed this unfortunately with the way the execution wrapper now
works. I believe Matt was looking at reverting the behavior to what it was
before when ANSIBLE_KEEP_REMOTE_FILE is set to true but I'm not sure where
he is at with that. Unfortunately this means in the meantime I'm stuck with
2.3 removed this unfortunately with the way the execution wrapper now
works. I believe Matt was looking at reverting to the older executor to
allow this debugging to work but not sure where he is up to. I've had to
either use Fail-Json statements everywhere and try and debug that way (not
likin
Good stuff, cheers. Will set aside some time tomorrow
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For mor
opened issue:
https://github.com/ansible/ansible/issues/23986
On Tuesday, April 25, 2017 at 11:18:59 PM UTC+2, Trond Hindenes wrote:
>
> Haha, glad to help
>
> Regarding check mode: Yep, please raise an issue in the dsc repo on github
> and I'll keep that updated. We'll be moving the win_dsc5 mod
Haha, glad to help
Regarding check mode: Yep, please raise an issue in the dsc repo on github
and I'll keep that updated. We'll be moving the win_dsc5 module into
Ansible core soon, but for now it lives in the repo
https://github.com/trondhindenes/Ansible-win_dsc
On Tuesday, April 25, 2017 at
