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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...