Open afrankgft opened 2 years ago
I did some testing with splunk 8.x, which does not seem to be properly deployable via this module. Given, that splunk 7.x is out of support since a while (see https://www.splunk.com/en_us/legal/splunk-software-support-policy.html#core ) it seems that this module won't be of any use.
I'm checking if I can find some time to check for adjustments.
When will this module support splunk version 7.3.x and 8.x.x and 9.x.x. The SplunkD service fail to start after deployment for version 7.3.x onwards as splunk has changed the enable boot_start from systemd back to init.d.
https://community.splunk.com/t5/Installation/Why-is-Systemd-broken-on-new-install/td-p/482881
Summary of the issue: Splunk 6.0.0 - Splunk 7.2.1 defaults to using init.d when enabling boot start Splunk 7.2.2 - Splunk 7.2.9 defaults to using systemd when enabling boot start Splunk 7.3.0 - Splunk 8.x defaults to using init.d when enabling boot start
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
I see in the documentation that the current tested and supported version of Splunk is 7.3 and OS is RHEL and CentOS 7 is there any testing or plan for both Splunk 8.x and version 8 of RH based operating systems?
What behaviour did you expect instead
Output log
Any additional information you'd like to impart