That dramatically increases complexity for sure. I won't have cycles to do it myself, but here's what I would like:

Client only

At least initially, only Windows clients would be supported. I don't know how well Splunk server runs on Windows, but I want to avoid needless complexity.

Installation

The splunk_installer definition needs support to install Windows
packages. This should use the native package resource with Windows
provider and filesystem location of the package (MSI, etc)

Helpers, Resource

The library helpers need to be extended for Windows paths. These should be done in the "Windows Way" of doing such things, and not break compatibility with the existing implementation.

As applicable, the splunk_app resource needs to be updated to support Windows. This may be abstracted sufficiently in the library helpers, though.

Test Coverage

ChefSpec: This should be the best covered place for tests. ChefSpec helps ensure we don't have regressions on other platforms.

Kitchen: Test Kitchen itself doesn't yet support Windows guests. There is an open pull request, but we must be able to automatically test Windows with Kitchen.

Serverspec: I believe Serverspec works on Windows, but I have no experience with it. The tests that exist now would automatically get run against Windows nodes, so that has to work.

from chef-splunk.

I'm looking at how this could be implemented. First obstacle is finding the download link that doesn't require authentication.

Linux

http://download.splunk.com/releases/6.2.1/universalforwarder/linux/splunkforwarder-6.2.1-245427-linux-2.6-x86_64.rpm

I've not been able to guess the URL for windows. The url the browser shows is

http://www.splunk.com/page/download_track?file=6.2.1/universalforwarder/windows/splunkforwarder-6.2.1-245427-x64-release.msi&platform=Windows&architecture=x86_64&version=6.2.1&product=splunk&typed=release&name=windows_installer

I'm assuming that it should look like this:

http://download.splunk.com/releases/6.3.3/universalforwarder/windows/splunk-6.3.3-f44afce176d0-x64-release.msi

from chef-splunk.

http://www.splunk.com/bin/splunk/DownloadActivityServlet?architecture=x86_64&platform=windows&version=6.3.3&product=universalforwarder&filename=splunkforwarder-6.3.3-f44afce176d0-x64-release.msi&wget=true

from chef-splunk.

Splunk recently changed the download URIs. Here's the one you're looking for:
http://download.splunk.com/products/splunk/releases/6.3.3/windows/splunk-6.3.3-f44afce176d0-x64-release.msi

from chef-splunk.

Instead of downloading the release directly, it would probably be better to use chocolatey packages.

https://chocolatey.org/packages/splunkforwarder

from chef-splunk.

I think that since the node attributes allow for specifying any download URL an implementer needs, this cookbook shouldn't have to be modified to accommodate any particular URL preference. As new versions are released, the default version and URL in this cookbook will constantly need to be updated, which can be easily done in a role or environment attribute setting or in a wrapper cookbook of choice.

The primary enhancement I think that is in scope for this cookbook is detecting when a splunk forwarder bundle is an MSI and using the appropriate package resource to install it. I don't know if there is a need to support installing splunk server on Windows, as I do not have experience with the server running on Windows either -- don't know many implementations where Splunk Server is installed on a Windows server, as well.

from chef-splunk.