Splunk Dev

App Inspect Error-check_inputs_conf_spec_stanzas_has_python_version_property

jabezds
Path Finder

Hi,

I am trying to validate my app with app inspect and im getting the following error, I have tried multiple solutions but couldn't get through.

Extract from App Inspect

[ Failure Summary ]
Failures will block the Cloud Vetting. They must be fixed.
check_inputs_conf_spec_stanzas_has_python_version_property

Modular input "cloudlock" is defined in README/inputs.conf.spec, python.version should be explicitly set to python3 under each stanza. File: README/inputs.conf.spec Line Number: 1


Modular input "cloudlock_health_check" is defined in README/inputs.conf.spec, python.version should be explicitly set to python3 under each stanza. File: README/inputs.conf.spec Line Number: 4


Modular input "destination_lists_health_check" is defined in README/inputs.conf.spec, python.version should be explicitly set to python3 under each stanza. File: README/inputs.conf.spec Line Number: 7


Modular input "investigate_health_check" is defined in README/inputs.conf.spec, python.version should be explicitly set to python3 under each stanza. File: README/inputs.conf.spec Line Number: 10

 

Following is my configurations in  README/inputs.conf.spec

[cloudlock://<name>]
Log_Level = INFO

[cloudlock_health_check://<name>]
Log_Level = INFO

[destination_lists_health_check://<name>]
Log_Level = INFO

[investigate_health_check://<name>]
Log_Level = INFO

 

Following is my configurations in input.conf

[cloudlock://incidents]
disabled = 0
interval = 60
Log_Level = INFO
python.version = python3

[cloudlock_health_check://health_check_cloudlock_batch_job]
disabled = 0
interval = 600
Log_Level = INFO
python.version = python3

[destination_lists_health_check://health_check_destination_lists_batch_job]
disabled = 0
interval = 600
Log_Level = INFO
python.version = python3

[investigate_health_check://health_check_investigate_batch_job]
disabled = 0
interval = 600
Log_Level = INFO
python.version = python3

 

Please help me with a solution .

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Looks like a bug in App Inspect as it appears to be treating inputs.conf.spec the same as inputs.conf, which is incorrect.  Open a case with Splunk, if you can.

---
If this reply helps you, Karma would be appreciated.
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...