Add-on builder: Why is Cloud vetting failing but no errors or failures in compatibility report?

[Shlifka]

Hello,

I submitted my Splunk Add-on for Cloud vetting. it is failed on both "VICTORIA" and "CLASSIC", however no errors or failures were found in the compatibility report:

Failures	0
Warnings	11
Errors	0
Not Applicable	42
Manual Checks	17
Skipped	0
Successes	143

I used the Splunk Add-on Builder and did not add any libraries myself. All warnings and manual checks are from within the add-on builder - aob_py3. example: 

Possible insecure HTTP Connection. Match: urllib2.urlopen Positional arguments, ["?"]; Keyword arguments, {"null": "?"} File: bin/ta_island_add_on_for_splunk/aob_py3/jsonschema/compat.py Line Number: 36

How can I understand why the vetting failed? How can I use the add-on builder to build an add-on that passes the cloud vetting?

Thank you, Omer.

[tshah-splunk]

I'm not sure why it failed. Try running the vetting using the private_app tag. That's the one needed for vetting the private apps on Cloud instances.

[Shlifka]

Hi, I used the included_tags=cloud.

It still doesn't explain why the official add-on builder creates an add-on that doesn't pass

How can I use aob_py3 that will pass it?

Thank you

[tshah-splunk]

Hey @Shlifka,

Can you let me know which tags were used while vetting the app? Also, I can see that there are 17 manual checks present in the vetting summary. Any private app will be self-service installable only if there are no Errors, Failures, or Manual Checks. Try fixing the manual checks and re-vet the app. It'll get installed successfully via self-service.