This value is read directly from a text file. If you read the file, increment the value, write it back, then start/restart splunkweb you will get the desired effect.
You may not need to do this as the install/upgrade should already be breaking the users cache as each version is included in the cache breaking mechanism.
For anyone following along at home. Here's a shell script I wrote to do increment the version number from the command line.
Here's the contents of do_bump.sh
:
#!/bin/bash
# Default splunk home if not already set
SPLUNK_HOME=${SPLUNK_HOME-/opt/splunk}
bump=`cat $SPLUNK_HOME/var/run/splunk/push-version.txt`
echo "Current version: $bump"
let bump++
echo -n $bump > $SPLUNK_HOME/var/run/splunk/push-version.txt
echo "New version: $bump (Restart splunkweb?)"
Since I ended up here, x-posting -- if anyone wants to do this with Javascript, it's far easier and doesn't require a splunkweb restart:
https://answers.splunk.com/answers/390115/how-do-you-programmatically-bump-a-search-head.html#answer...
This value is read directly from a text file. If you read the file, increment the value, write it back, then start/restart splunkweb you will get the desired effect.
You may not need to do this as the install/upgrade should already be breaking the users cache as each version is included in the cache breaking mechanism.
It looks like push-version.txt
is the file you are talking about. I've added an answer with a simple script to do increment this value. Thanks for leading me in the right direction. (BTW, I think I often forget to replace the "favicon.ico" until after I've started splunk after an upgrade, so I'll add this logic to my "post-install" script and that should make sure the right icon gets seen by the users.)