The classic playbook editor will be deprecated soon. Convert your classic playbooks to modern mode.
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:
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:
Download topic as PDF
Prerequisites for migrating from Splunk Phantom to Splunk SOAR (Cloud)
Before you can carry out a migration of your Splunk Phantom administration settings, applications, playbooks, and custom functions you must perform the following tasks:
- Convert all Splunk Phantom custom apps to use Python 3. See Convert apps from Python 2 to Python 3 in the Develop Apps for Splunk Phantom manual.
- Convert all playbooks and custom functions to use Python 3. See Convert playbooks or custom functions from Python 2 to Python 3 in the Python Playbook API Reference for Splunk Phantom manual.
- (Optional) Use a a cloud or internet-facing Git repository for source control for ease of migration and standardization for development best practices.
- To configure source control on your existing Splunk Phantom instance, see Configure a source control repository for your Splunk Phantom playbooks in the Administer Splunk Phantom manual.
- If you decide not to use a Git source control repository, you must import each playbook either through the user interface or through scripts from the REST API. See REST Playbook in the REST API Reference for Splunk Phantom manual.
Last modified on 27 March, 2024
|
PREVIOUS Restrictions within Splunk SOAR (Cloud) |
NEXT Migrate Splunk Phantom administration settings to Splunk SOAR (Cloud) |
This documentation applies to the following versions of Splunk® SOAR (Cloud): current
Feedback submitted, thanks!