Unsupported Platform - windows about kitchen-puppet HOT 9 CLOSED

Looks like unsupported platform part directly relates to #94 .
@grubernaut let's decide how to proceed here

from kitchen-puppet.

@grubernaut my proposal #99

from kitchen-puppet.

I've also created #100 to address enhancement side separately

from kitchen-puppet.

@Lucky27 feel free to try out #99 , it should fix your issue with unsupported platform failure

from kitchen-puppet.

Currently we don't have windows support but it should not be difficult to add.
Unfortunately my laptop is not powerful enough to run the full windows 2012r2 virtual box.
i can run windows nano but you have to use remote powershell to install openssh etc as the winrm support doesn't work.
i'll look to see if i can run some other windows version under virtual box.

from kitchen-puppet.

@ytsarev I tried using #99, unsupported error is gone but it is throwing a different error now.

https://gist.github.com/lucky27/27141a1affadcf85d93d

@neillturner We use lot of windows modules, so adding windows support would be lot helpful for us.
Please let me know If u need any help with testing code on windows platforms.

Also I have another question, right now our folder structure is we have manifest folder(with contents of module I want to test) and modules folder with dependencies. I would like to add a site.pp file to all our modules, which has some custom settings like our inhouse chocolatey-nuget repository and other settings. Where should I add this? and how should I use it in the .kitchen.yml file?

from kitchen-puppet.

a couple of questions:

1. how do you install puppet on your windows servers. msi, choclately or ruby and puppet individually?
2. when you access your server via ssh is puppet in the path and available to execute.

I was thinking of creating a minimal windows version that assumes that puppet is install and available on the path.

kitchen puppet has 2 parameters:
manifest which defaults to 'site.pp' which is the initial manifest that is run.
manifests_path: which defaults to the top level folder.

you can see an example in https://github.com/neillturner/puppet_repo
where there is a manifests folder containing site.pp
and the .kitchen.yml file has parameter
manifests_path: manifests

from kitchen-puppet.

@neillturner I use chocolatey to install it and yes puppet is available on path.

Below is the puppet module structure I want to add, development folder has site.pp which has global settings and manifests/init.pp file contains the current module..how should I add these 2 in .kitchen.yml ? modules folder has the dependency modules.

from kitchen-puppet.

closing this in favour of Windows Support #79

from kitchen-puppet.