After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Upgrade a Splunk SOAR (On-premises) instance
Follow these steps to upgrade your unprivileged instance, or to convert and upgrade your existing, privileged instance to an unprivileged instance. Use these steps even if your unprivileged instance has limited access to the internet. The installation TAR file contains everything needed to complete this upgrade.
The same TAR file is used for install and upgrade processes. The file detects the presence of SOAR and installs or upgrades accordingly.
If you have already downloaded and extracted the installer package to migrate your privileged instance to unprivileged, you can move straight to step 10 and run the install script.
- Read upgrade overview and prerequisites.
- Prepare your system for upgrade. See Prepare your Splunk SOAR (On-premises) deployment for upgrade.
- Restart the operating system if you did not recently restart it as part of the preparations in Step 2.
This step is required to ensure that the upgrade completes successfully and efficiently.
As the root user:reboot
- After the system restarts, log in to the operating system as the user that owns Splunk SOAR (On-premises). Do not perform the upgrade as the root user.
- Download the unprivileged installer from the Splunk SOAR site. The unprivileged installer prepackages its dependencies and can be installed on systems that cannot reach out to the internet.
The unprivileged installer is named in the formatsplunk_soar-unpriv-<major>.<minor>.<patch>.<build>-<commit_short_sha>-<os>-x86_64.tgz
. - Conditional: If you have previously upgraded this instance of Splunk SOAR (On-premises), you may still have a directory at <$PHANTOM_HOME>/splunk-soar. If that is true, remove that directory.
rm -rf <$PHANTOM_HOME>/splunk-soar
- Extract the TAR file you downloaded into the Splunk SOAR (On-premises) installation directory. Extracting the TAR file this way creates a new directory in the Splunk SOAR (On-premises) home directory, <$PHANTOM_HOME>/splunk-soar.
tar -xvf <installer>.tgz -C <$PHANTOM_HOME>
- Make sure that that your current installation of is running.
<$PHANTOM_HOME>/bin/start_phantom.sh
- Change directory to the <$PHANTOM_HOME>/splunk-soar directory.
cd <$PHANTOM_HOME>/splunk-soar
- The installer package you extracted creates a file called soar-install in the <$PHANTOM_HOME>/splunk-soar directory. Run that script.
./soar-install --upgrade --with-apps
- Conditional: If you extracted the installation TAR file to a different directory than <$PHANTOM_HOME>/splunk-soar, you must supply the path to your Splunk SOAR (On-premises) installation to the installation script.
<path/to/extracted/TAR file>/soar-install --splunk-soar-home <path/to/$PHANTOM_HOME> --upgrade --with-apps
You can see the full list of arguments for the soar-install script by using the
--help
option.
- Conditional: If you extracted the installation TAR file to a different directory than <$PHANTOM_HOME>/splunk-soar, you must supply the path to your Splunk SOAR (On-premises) installation to the installation script.
- After the upgrade is complete, remove installation package by deleting the <$PHANTOM_HOME>/splunk-soar directory.
rm -rf <$PHANTOM_HOME>/splunk-soar
Convert a privileged Splunk SOAR (On-premises) deployment to an unprivileged deployment | Upgrade a Splunk SOAR (On-premises) cluster |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.0.1
Feedback submitted, thanks!