@christopherrobe, I want to start by thanking you for this info! I spent a lot of time trying to figure out what was going on with my app in our production instance (clustered) that was completely fine in my local standalone instance. Like you, I noticed that when using a non-streaming command, like `noop` or `head`, before my CSC that this worked fine in the clustered instance. There are a few things however that make me concerned about putting splunklib under /bin. First, AppInspect throws a warning if you move the splunklib folder under /bin: {
"description": "Check splunklib dependency should not be placed under app's bin folder. Please refer to\n https://dev.splunk.com/view/SP-CAAAER3 and https://dev.splunk.com/view/SP-CAAAEU2 for more details/examples.",
"messages": [
{
"code": "\"splunklib is found under `bin` folder, this may cause some dependency management \"",
"filename": "check_application_structure.py",
"line": 228,
"message": "splunklib is found under `bin` folder, this may cause some dependency management errors with other apps, and it is not recommended. Please follow examples in Splunk documentation to include splunklib. You can find more details here: https://dev.splunk.com/view/SP-CAAAEU2 and https://dev.splunk.com/view/SP-CAAAER3",
"result": "warning",
"message_filename": null,
"message_line": null
}
],
"name": "check_splunklib_dependency_under_bin_folder",
"tags": [
"splunk_appinspect",
"cloud",
"private_app"
],
"result": "warning"
}, The second concern is that the guide at https://dev.splunk.com/enterprise/docs/developapps/appanatomy/#Considerations-for-Python-code-files also instructs the user to put splunklib under /lib. Since the AppInspect message tells you there may be dependency issues putting splunklib in /bin, yet it appears this is necessary for streaming CSCs to work in clustered environments, is there some underlying issue that needs to be addressed?
... View more