Release notes for the Splunk Python Upgrade Readiness App

The Python Upgrade Readiness App version 2.0.0 was released on July 24th, 2021. This version is compatible with Splunk Enterprise versions 7.3, 8.0, 8.1 and 8.2 and higher, and Splunk Cloud Platform 8.2.2107 and higher.

Known issues and troubleshooting

This section tells you how to deal with some common issues in Splunk Python Upgrade Readiness App 2.0.0.

Error message appears in UI after upgrade

Upon upgrade from version 1.0.0 to version 2.0.0, the following error message can appear in the UI:

name 'MERGED_DIR' is not defined

If you receive this error message, wait 4 to 5 minutes for the report to load. If the report is not generated, an appropriate message appears.

Change the frequency of Splunkbase metadata

To fetch the Splunkbase metadata more frequently, modify the interval setting in the following scripted input stanza in inputs.conf:

script://$SPLUNK_HOME/etc/slave-apps/python_upgrade_readiness_app/bin/pura_get_all_apps.py

After updating the interval, you must restart Splunk.

For more information on scripted inputs, see inputs.conf

For help setting the interval in cron format, see https://crontab.guru

Convert a public app to a private app

You can convert a public app to a private app for scanning purposes, as follows:

1. Add the public app (folder) to the lookup file at the following location:

   $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/lookups/pura_mark_public_as_private.csv
   

2. Run the following search:

   | stats count | eval app_folder_name = "<name of application folder>" | table app_folder_name | outputlookup append=true pura_mark_public_as_private