9.2.24

Standardise files with files in sous-chefs/repo-management

Standardise files with files in sous-chefs/repo-management

9.2.23

Standardise files with files in sous-chefs/repo-management

Standardise files with files in sous-chefs/repo-management

Standardise files with files in sous-chefs/repo-management

9.2.22

Update metadata for 9.2.22

9.2.21

Update metadata for 9.2.21

Fixes Issue #128

Fixes logic in #shcluster_members? helper method with a better match

Only link /etc/systemd/system/splunk.service running on systemd

• Fix centos-6 and Amazon linux convergence by adding an only_if to only create systemd symlinks on systemd systems.
• Adds clarification text to README.md regarding chef-vault fallback to encrypted data bags
• Changes the build status badge to track Actions status

Expand and correct suite failures so all supported OSes are covered + split suites between Vagrant and Dokken

Description

• Add missing supported OSes from the test matrix (Fixes: #194).
• Move all suites expect those that don't run as root back to dokken, as running as non-root fails in dokken.
• Add missing suites from the kitchen config to the matrix.
• Remove post_converge from the dokken config, as it's gone from the vagrant config.
• Ensure same platforms are listed in the dokken and vagrant kitchen configs.
• Sync up the suite names in ci workflow and suites (change _ to -).
• Correct test failure for server-runas-splunk where command failed due to permission error writing to /root/.splunk/.

Issues Resolved

That tests are carried out on more supported OSes (expect centos-6, as it's EoL on 2020-11-30).

BREAKING CHANGE: v7.0.0

• sets umask when executing the execute[splunk enable boot-start] resource
• adds new attribute, default['splunk']['enable_boot_start_umask'] for umask setting applied to execute[splunk enable boot-start] (Default: '18')
• BREAKING CHANGE #splunk_cmd now requires a dynamic array of arguments that will be appended to the splunk command
• splunk.service is symlinked to the systemd unit
• adds a kitchen-vagrant config to run inside Github Actions
• enhancements to the :remove action for splunk_installer resource to ensure a complete uninstall for both Splunk Enterprise Server and Universal Forwarder

v6.4.1 Bugfix: running splunk as non-root user

• Fixes an issue running Splunk and the Splunk Universal Forwarder as a non-root user
• Fixes Test Kitchen configuration to test running Splunk as non-root user
• Helper methods in libraries/helper.rb are moved to their own module space: ChefSplunk::Helpers
• Disables Splunk management port (8089) when installing the Universal Forwarder

v6.4.0

• Fixes Issue #185
  • a startup issue was resolved for SplunkForwarder installations with an improved
    systemd unit file (fix below)
  • Adds Inspec tests to verify from SplunkForwarder starts (thanks, @jjm)
• Fixes Issue #187
  • the systemd unit file is now relegated to the splunk enable boot-start command to manage
• Adds Inspec tests and sets the verifier in Test Kitchen for some test suites; some are still in serverspec
• Render the user-seed.conf with a file resource rather than a template
• The default recipe no longer includes the disable recipe; to disable splunk, add recipe[chef-splunk::disabled] to a run list explicitly
• Disabling splunk will no longer uninstall Splunk Enterprise nor the Splunk Universal Forwarder
• Adds #SecretsHelper to aid with secrets rotation and maintaining idempotency for handling Splunk's hashed secret values
• Improved guards to prevent service[splunk] restart/start when it should be disabled.