Skip to main content

 

Splunk Lantern

Upcoming changes for Splunk Cloud Platform version 10.7

This article provides a summary of changes to Splunk Cloud Platform coming in version 10.7. The article includes detailed information about the nature of these changes, the parties that the changes affect, and any necessary mitigation strategies. The objective of this article is to help you plan and act promptly.

Potentially breaking changes

Customers and app developers alike should carefully review all changes in this section as you prepare to migrate to Splunk Cloud Platform version 10.7 since there is a potential for disruption.

Deactivation of Python version 3.9 by default in Splunk Cloud Platform

Summary: Splunk Cloud Platform version 10.7 turns off version 3.9 of the Python interpreter by default. Python 3.14 becomes available as an opt-in interpreter.

Overview: After an upgrade to Splunk Cloud Platform version 10.7, version 3.9 of the Python interpreter is no longer available by default. Splunk apps and Technology Add-ons that depend on Python 3.9 might run incorrectly or fail entirely. Python 3.13 remains the default supported interpreter. Python 3.14 is available as an opt-in interpreter. Splunk Cloud Platform customers who need additional time to migrate to a supported interpreter can open a Support ticket to temporarily restore support for Python 3.9 for an affected deployment.

Affected customers: Splunk Cloud Platform app and Technology Add-on developers, and customers whose apps depend on Python 3.9.

Issue detection and mitigation guidance: Identify apps and Technology Add-ons that depend on Python 3.9, test them with supported Python versions, and migrate them before upgrading to Splunk Cloud Platform version 10.7. Splunk Cloud Platform customers who need more time can open a Support ticket to temporarily restore Python 3.9 availability for an affected stack while completing migration.

For more information on how to configure a Python interpreter for your Splunk apps, see Specify Python compatibility for your app. For information on how to review Python compatibility for your app in Cloud Management Console, see Review health indicator details.

Federated provider name case-insensitivity enforcement

Summary: Customers with duplicate federated provider names that differ only by case might see federated searches fail with a message to update or remove the duplicate name.

Overview: Starting in Splunk Cloud Platform version 10.7, Federated Search enforces case-insensitivity for provider names. Mixed-case or uppercase provider names in the federated.conf and indexes.conf configuration files can cause federated datasets to enter an unknown status, searches to fail with invalid dataset specifier errors, and new dataset or index creation to be rejected. This change restores backward compatibility for pre-existing configurations by enforcing consistent naming.

Affected customers: Customers with duplicate federated providers that differ only by case, and administrators using Federated Search and Federated Analytics paths (FS-S2S, FS-S3, FS-SAL, and FA-ASL).

Issue detection and mitigation guidance: No customer-side remediation is required for the corrected behavior. If you have duplicate providers that differ only by case, follow the specific error message that the Splunk platform provides to update or remove the duplicate name.