What's new in the Splunk AppInspect API

This topic summarizes the changes included in each version of the Splunk AppInspect API.

v2019.08

There are no new features in this release of the Splunk AppInspect API.

See Splunk AppInspect API known issues for known issues in this release.


v2019.06

New features and enhancements

Using AppInspect API for app validation also includes all the new features and enhancements in the latest AppInspect CLI tool release in addition to what's listed in this section. See What's New in AppInspect CLI tool for details.

  • This release of the AppInspect REST API works with version 1.7.1 of the AppInspect CLI tool.
  • The AppInspect REST API service now returns more specific status codes and descriptions for each authentication request. Previously, when the return code was not 200, the AppInspect REST service only returned a generic status code (401) and description (Failed to authenticate).
  • Python 2 will reach End of Life (EOL) in 2020. Future releases of Splunk Enterprise will support Python 3, and all apps must be Python 3 compatible to properly run on Python 3 Splunk platforms. For information about Python 3 migration and its impact on Splunk Enterprise, see Python Migration with the Splunk Platform in the Splunk Enterprise Python 3 Migration Guide.

    This release of AppInspect provides the following checks (tagged "py3_migration") to perform a preliminary assessment of Python 3 readiness of your apps:

    • check_for_advanced_xml_module_elements
    • check_for_splunk_web_legacy_mode
    • check_for_app_packages_static_endpoint
    • check_for_reserved_filename_test_py
    • check_for_removed_m2crypto_usage
    • check_for_cherry_py_custom_controller_web_conf_endpoints
    • check_for_existence_of_mako_template
    • check_py2_command_scripts_and_scripted_lookup_exist
    • check_for_python_script_existence
    See Splunk AppInspect check criteria for details. These checks currently do not cover all the areas impacted by the Python 3 migration and more Python 3 compatibility checks will be added in future releases.
    Like all other checks, you can use either the AppInspect REST API (recommended) or the AppInspect CLI tool to perform Python 3 readiness checks (tagged "py3_migration") to review your apps for compatibility with Python 3.
    For detailed instructions, see Run Splunk AppInspect requests through the API and Use the AppInspect CLI tool respectively.

v2019.04

From this version forward, the AppInspect API is released separately from the AppInspect CLI tool to communicate API changes to the user in a more timely fashion. In previous releases, despite more frequent updates on the API side, the user had to wait until the next AppInspect API and CLI tool release to be informed of the changes.

New features and enhancements

Using AppInspect API for app validation also includes all the new features and enhancements in the latest AppInspect CLI tool release in addition to what's listed in this section. See What's New in AppInspect CLI tool for details.

  • This release of the AppInspect REST API works with version 1.7.0 of the AppInspect CLI tool.
  • Enables Google Safe Browsing API service to identify malicious URLs in apps
  • Identifies lookups created on the fly before running saved searches for validation
  • Adds callback URL support for API requests
  • Better handling of repeated requests in a certain period of time to avoid duplication
  • Updated API Swagger UI
  • Java runtime service updated to jre-8
  • Enhancements made to the Splunk Enterprise instances for validating apps:
    • Splunk Enterprise version upgraded to 7.1.0
    • CIM 4.12.0 installed as a prerequisite component
    • ES dependencies integrated
    • Guarantees Splunk KV store readiness before app inspection