Splunk Dev

Is it necessary to put `shebang` on custom scripts?

morethanyell
Builder

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.

Labels (3)
0 Karma
1 Solution

PickleRick
SplunkTrust
SplunkTrust

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)

View solution in original post

0 Karma

PickleRick
SplunkTrust
SplunkTrust

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)

0 Karma
Get Updates on the Splunk Community!

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...

Adoption of Infrastructure Monitoring at Splunk

  Splunk's Growth Engineering team showcases one of their first Splunk product adoption-Splunk Infrastructure ...