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!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...