Hi,

I mostly just create playbooks having sshed into a virtual machine.  We 
keep the entire ansible configuration (inventory, playbooks, roles, custom 
modules and plugins etc) in Mercurial (mandated version control where I 
work).  For a while I used to edit playbooks on windows using Notepad++ 
which has yaml syntax highlighting and then use mercurial commit push then 
switch to the vm and do pull and update to run the playbooks, but I tend to 
just use the vm now I'm more confident that I can write valid yaml and the 
feedback cycle is faster.
I used putty for long time to connect, but have recently started using 
cmder (cmder.net) which lets you have multiple tabs open against the 
machines (I often have 1 pty for running playbooks and another couple for 
editing files).

Very shortly the anniversary update to windows 10 will be out, and with 
that the ability to run ubuntu within windows.  I've tried it out on an 
Insider build and its certainly good enough to develop playbooks in and run 
them against a few windows hosts.  Once it is available in official 
released window 10, I intend trying it out to see if I can make a slicker 
development workflow.

Hope this helps,

Jon

On Wednesday, August 3, 2016 at 6:51:57 PM UTC+1, Brian Jackson wrote:
>
> I'm new to Ansible and I spend my days on a Windows workstation. Our 
> company is adopting Ansible because one large section of the company uses 
> Linux for servers and workstations. I'm in a smaller section that has a mix 
> of Windows and Linux servers but mostly everyone has Windows workstations. 
> Is anyone else developing Ansible playbooks on Windows yet? I think the 
> answer is "no" since Ansible Control Machine doesn't run on Windows. So how 
> do those that have Windows workstations develop new playbooks? Do you forgo 
> a BDD style of work? Ideally I want to follow a development style similar 
> to this example using Vagrant: https://www.youtube.com/watch?v=tNCDsnQvbHI, 
> but can't on Windows.
>
> Thanks for any advice,
> Brian
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/efc8748f-51de-46ce-aead-6200704481f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to