Just to say I rebased https://github.com/ansible/ansible/pull/9611
Sorry its taken a while to get to it.
Jon
Just in case anyone is following this thread, win_copy, win_file and win_template have now been merged into dev.
Thanks everyone.
Jon
Yeah we just had a discussion about this.
I think we’re going to (temporarily) un-merge, and look into the copy-paste code de-duplication first.
(They were also merged into -core, and really should be -extras first, which mostly was because the PRs were made to the wrong spots)
Hi all,
I apologize in advance for the dumb question. I’ve been tasked at work to look at supporting Windows servers with Ansible. I started simple by trying to configure and install CouchDB on Windows. So far I like the agent-less model.
I now need to be able to upload files and tweak configurations via the template module. Which Ansible branch can I look at to try the win_copy, win_file and win_template modules?
I’ve tried the devel branch (at commit 1698b17b1475e833b3b2930d723e047d7ff36b9e ) but it does not seem to contain the modules that I am looking for.
I am getting an error like: ERROR: win_copy is not a legal parameter in an Ansible task or handler
I am sure this is a stupid configuration error from my part, but I can’t work out how to make it work ( my Python and PowerShell scripts are not very good I am afraid).
Thanks in advance,
Guillaume.
Hi Guillaume,
The win_copy module was reverted and pull out of the repos. So you most likely cannot find it now. I had tested it at some point and could not get it to work.
However, I am still very curious about this module because it would be so useful. Is there any word on the latest of this module development? I’d like to see the source, maybe even pull it into devel at ansible-modules-extras so that others could contribute to it and test.
It was only in the repo for a couple days before being merged into core and then reverted like the next day.
Thanks,
Phil
Hi,
+1
I’m also interested in this and might get some time to help test so I +1 for having it on a branch.
Thanks
We’re not going to likely hit this until the ‘v2’ tree is complete, as we do think it needs to inherit from other modules, but we need to take time to look at the architecture of how this is implemented in the new tree.
Thanks for the update Michael.
For the time being, I am applying the template locally (on the Linux ‘master’ node) and I serve the template output via a web server using the win_get_url module. It feels a bit like a hack, but it actually works quite well.
Is there a time frame for the completion of the v2 tree?
Cheers,
Guillaume.
Yep!
v2 is going to be done for 1.9 (undecided on whether we call this a “2.0”, but our goal is to have it 99.X% compatible) … we hope to have it in a state where people can help test and contribute to it in a month or so (approximately).
–Michael
Hi!
1.9 rc1 has just been released on GitHub, but I don’t see any extra windows modules shipping with it. Is there any update on your “schedule”?
Thanks, Martin
I would also like to know when this stuff will be out please.
– Sent from a mobile device –
My understanding is this.
The plan was to tackle the common logic issue (specifically so that template and win_template can share as much code as it makes sense to share and any other action plugins that we may well want to have different implementations of for windows) in the v2 codebase. 1.9 is still using the older codebase.
So when 1.9 is released and v2 becomes the current development version this can be tackled.
That said, the win_copy and win_template action plugins have been merged into 1.9 rc so that the action plugins can be worked on once v2 is there to support the necessary changes.
This means that if you really want to try win_copy / win_file / win_template you can grab them from https://github.com/ansible/ansible-modules-core/pull/384 into your /etc/ansible/library. Obviously these may well change and you may or may not have to fix your playbooks to work with the supported versions.
If you do try this, be aware of the following.
If you need windows line endings (\r \n)
1/ put the following on the first line of your template:
#jinja2: newline_sequence:‘\r\n’
2/ If your template file was created on a windows machine, remove the byte order mark if present (will be the first hidden character of the file) as this trips up Ansible. You can see if this is present using od -cx
Jon
v2 is now in active development, but u don't see mention of win_copy/file/template in the CHANGELOG. Any updates whether this will get integrated?
+1. It would be great seeing these modules pulled in.
In case anyone is still watching this thread, win_copy, win_file and win_template have now been merged into latest devel.
Jon
Nice!
Did it get back ported to v1?
$ find . -name "win_copy*" ./lib/ansible/modules/core/windows/win_copy.ps1 ./lib/ansible/modules/core/windows/win_copy.py ./v1/ansible/modules/core/windows/win_copy.ps1 ./v1/ansible/modules/core/windows/win_copy.py ./v1/ansible/runner/action_plugins/win_copy.py