4 ms·
I just pushed a fix for this. If you pull, you should be good to go. The bug was introduced in the new version of Ansible that came out two days ago. I didn't c
by jlund 12y ago
I just pushed a fix for this. If you pull, you should be good to go. The bug was introduced in the new version of Ansible that came out two days ago. I didn't catch it because I hadn't updated quite yet. Sorry about that!
Edit: I'm still working through a few other Ansible 1.6.8 issues as well.
Edit 2: I think that I got them all.