Recently I read a bit about the Splunk Packaging Toolkit (http://dev.splunk.com/view/packaging-toolkit/SP-CAAAE9V) and got to know that apart from a lot of other utilities, it can also be used to declare your app dependencies using an app.manifest file. Has anyone tried declaring app dependencies using this toolkit before?
I have an app that's divided into three parts (dashboards app, TA, TA for Adaptive Response). I want to be able to define simple dependencies within these apps that would warn the user by telling something like 'TA is a required app for using TA-AR. Please install TA before proceeding with TA-AR installation'.
From all that I've read about the app.manifest file, it allows the developer to define a dependencies stanza and list all required apps. However, I haven't been able to find any examples of how to write this file, where to place it in the app directory structure and whether or not app.manifest can be defined without using the entire Splunk Packaging Toolkit.
Thanks a lot, alacercogitatus. I see you mentioned that this is a framework for later. Is it supported on Splunk Enterprise 6.5?
The reason I ask this question is that I'm using Splunk Enterprise 6.5 right now and after I copied the above app.manifest in my TA-AR (with some changes) and defined dependencies on my TA, I see no warnings on installation.