I have seen clients do this by setting up a cron job to run every hour/half-hour:
/opt/splunk/bin/splunk apply cluster-bundle
If there have been no changes to the folder's contents, applying the cluster bundle doesn't do anything (Since the hash of the folder's contents match the hash of the currently applied cluster bundle, so there is nothing to and the bundle-apply process exits).
There is the risk that with automating like this that if the deployment server sends down certain types of changes down to the cluster mater, it'll initiate a rolling-restart. This link will detail what might cause that: Restart or reload after configuration bundle changes?
I'd recommend testing this before going live with the change as there may be something specific to your environment that may cause issues.
... View more