You must make sure the custom function or playbook is working correctly before proceeding. Test each custom function and playbook before converting them.You will need this backup in order to restore your git repositories and their contents in the event that there is a problem during the conversion. Create a full backup of your Splunk Phantom deployment.Here are several best practices for doing the conversions. Splunk Phantom 4.10 and later contains two phenv commands to help you convert your custom functions and playbooks from Python 2 to Python 3.īest Practices for converting Splunk Phantom playbooks and custom functions from Python 2 to Python 3Ĭonverting custom functions or playbooks to Python 3 requires some planning and careful work on both ends of the conversion process. Many deployments have significant numbers of playbooks and custom functions which were developed in Python 2 that need to be updated to Python 3. Because Python 2 is "end of life," you should consider converting your playbooks and custom functions to Python 3. Splunk Phantom 4.10 maintains a runtime environment for both Python 2 and Python 3 playbooks and custom functions. Python 2 is supported for playbooks and custom functions. The Splunk Phantom platform switched to Python 3 for in the 4.9 release and with the 4.10 release new playbooks and custom functions default to Python 3. Python 2 reached end of life status on January 1, 2020. Convert playbooks or custom functions from Python 2 to Python 3
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |