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:
Migrate Splunk Phantom playbooks and custom functions to Splunk SOAR (Cloud)
Perform the following steps to migrate Splunk Phantom playbooks and custom functions to Splunk SOAR (Cloud):
- Convert playbooks and custom functions to Python 3 in your Splunk Phantom instance before importing them to Splunk SOAR (Cloud). You might have completed this step as part of the prerequisites for migration. See Prerequisites for migrating from Splunk Phantom to Splunk SOAR (Cloud).
Ensure any import modules that require standalonephenv python pip install
installations have been either removed or migrated to an appropriate application wheels module. See Convert playbooks or custom functions from Python 2 to Python 3 in the Python Playbook API Reference for Splunk Phantom. Error notifications are present for playbooks or custom functions trying to import standalone pip libraries. - (Optional) Configure a cloud based or internet facing HTTP or HTTPS Git compliant repository for playbook use and development. Use a private repository to help ensure that your playbook code is not public or internet facing, and use common continuous improvement and continuous development models to improve development and roll out of production playbooks.
- Test and validate converted playbooks and custom functions in Splunk SOAR (Cloud).
Migrate Splunk Phantom applications to Splunk SOAR (Cloud) | Onboard Splunk Cloud Platform or Splunk Enterprise Security data |
This documentation applies to the following versions of Splunk® SOAR (Cloud): current
Feedback submitted, thanks!