Splunk Dev

AppInspect vs Upgrade Readiness App Results

superducktoes
New Member

I have an app that the Upgrade Readiness App says is not passing due to an error. After digging into it more it looks like it's occurring because of the line contrib/jquery-2.1.0 in the file /appserver/static/js/build/common.js

If I submit the same app to AppInspect, it doesn't have any results in the errors/warnings or in the manual checks for that line in common.js.

Really my question is, I believe common.js comes from the Add-on Builder. Is it okay to leave that file as is or do I just change the line referencing contrib/jquery-2.1.0 to use an updated version of jQuery?

Labels (1)
0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

I recently found that if you generate with the latest version of Add-on Builder, it should not have this problem from the Splunk developers. (Though I'm yet to test myself)

https://github.com/splunk/addonfactory-ucc-generator/issues/421#issuecomment-1033799650

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...