puppet will create outputs.conf and delete it immediately which causes splunk to restart every puppet run

[jemyers]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 5.5.18
• Ruby: 2.4.9
• Distribution: RHEL 6.10
• Module version: 8.0.0

How to reproduce (e.g Puppet code you use)

class { '::splunk::forwarder':
splunk_user => $splunk_user,
purge_outputs => false,

What are you seeing

Notice: /Stage[main]/Splunk::Forwarder::Config/File[/opt/splunkforwarder/etc/system/local/outputs.conf]/ensure: created (corrective)
Info: /Stage[main]/Splunk::Forwarder::Config/File[/opt/splunkforwarder/etc/system/local/outputs.conf]: Scheduling refresh of Class[Splunk::Forwarder::Service]

/Stage[main]/Splunk::Forwarder::Config/File[/opt/splunkforwarder/etc/system/local/outputs.conf]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Info: /Stage[main]/Splunk::Forwarder::Config/File[/opt/splunkforwarder/etc/system/local/outputs.conf]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Info: /Stage[main]/Splunk::Forwarder::Config/File[/opt/splunkforwarder/etc/system/local/outputs.conf]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Notice: /Stage[main]/Splunk::Forwarder::Config/Splunkforwarder_output[tcpout_defaultgroup]/ensure: created (corrective)
Info: /Stage[main]/Splunk::Forwarder::Config/Splunkforwarder_output[tcpout_defaultgroup]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Notice: /Stage[main]/Splunk::Forwarder::Config/Splunkforwarder_output[defaultgroup_server]/ensure: created (corrective)
Info: /Stage[main]/Splunk::Forwarder::Config/Splunkforwarder_output[defaultgroup_server]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Info: Class[Splunk::Forwarder::Config]: Scheduling refresh of Class[Splunk::Forwarder::Service]
Info: Class[Splunk::Forwarder::Service]: Scheduling refresh of Service[splunk]
Notice: /Stage[main]/Splunk::Forwarder::Service/Service[splunk]: Triggered 'refresh' from 1 event

What behaviour did you expect instead

How to correct this issue.

Any additional information you'd like to impart

I have tried the fix mentioned in #157 but the splunk module does not apply the purge_outputs value.