Is it necessary to put `shebang` on custom Python script that will be executed by `splunk`? The reason why I ask is because `shebang` is `#!/usr/local/bin/python` but we know that Spunk uses the one $SPLUNK_HOME/bin/python3.
Thanks in advance.
The correct form of shebang for python3 is
#!/usr/bin/env python3
But that's not the main point here.
Splunk should spawn its own python instance for python script regardless of the shebang (and shebang allows for easy testing outside of splunk environment)
The correct form of shebang for python3 is
#!/usr/bin/env python3
But that's not the main point here.
Splunk should spawn its own python instance for python script regardless of the shebang (and shebang allows for easy testing outside of splunk environment)