Erasmith Add-on for WMI Exporter - Pending Status & Missing Failure Report

[AstinSebastian]

Our application, Erasmith Add-on for WMI Exporter, is showing as Pending for both Victoria and Classicon in Splunkbase. Under the details, it indicates 2 failures, but the failure report is not available.

Additionally, during local cloud vetting, no errors or failures were observed.

Could anyone guide me on what steps I should take next to resolve this issue?

[livehybrid]

Hi @AstinSebastian 

I have recently had to wait 4 weeks for my Splunkbase submissions to be reviewed, this is typically due to manual_checks, when I ran AppInspect against your app it looks like there are 2 manual checks to be done, such as:

Security vulnerabilities
    Check for insecure HTTP calls in Python.
        MANUAL_CHECK: Possible insecure HTTP Connection. Match: requests.get
            Positional arguments, ["?"]; Keyword arguments, {"timeout": "?"}
            File: bin/wmi_exp.py Line Number: 38
        MANUAL_CHECK: Possible insecure HTTP Connection. Match: requests.get
            Positional arguments, ["?"]; Keyword arguments, {"timeout": "?"}
            File: bin/wmi_exp051224_working.py Line Number: 23

This will get assigned to a Splunk Engineer who manually vets the code and then will either pass or fail it, you will get an email notification once this has been completed.

Did you know that you have also included "wmi_exp051224_working.py" in your app within the /bin directory?

This has a hard-coded windows path for a config_file variable passed to the system open() function, this might also cause a manual check, and potential failure due to hard-coded windows path which is not compatible with Cloud.

Please let me know how you get on and consider accepting this answer or adding karma this answer if it has helped.
Regards

Will

[kiran_panchavat]

@AstinSebastian 

All apps uploaded to Splunkbase are automatically added to the Cloud Vetting queue. However, due to a significant backlog, apps that are not associated with customer installation requests and require manual vetting may remain in a pending state for an extended period. On the other hand, if your app has no manual_check results and no errors or failures, it can be automatically marked as compatible with one or both Splunk Cloud architectures, effectively bypassing the manual vetting queue. Of course, if your app encounters any errors or failures, you will receive an automated failure notification.