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.
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...

Level Up Your Workflow: Mastering Splunk Cloud Management via Terraform

Tech Talk Recap   From Chaos to Control: Scaling Splunk Cloud with Infrastructure as Code Managing apps in ...