Splunk Dev

What should be in my .gitignore for a new app/add-on?

Wilcooley
Path Finder

I'm importing an unmaintained app into my own git repo (there is no upstream, AFAICT) and there are a handful of files that are generated and should be ignored in any working copy?

This is what I have so far for my .gitignore:

local/
metadata/local.meta
# Maybe?
viewstates.conf
# This is added automatically when the app is uploaded, isn't it?
default/MANIFEST

What else?

I realize this is probably somewhere in the documentation, but it's probably spread over several different sources.

bmacias84
Champion

So we use git for all configuration files and apps for splunk. Here's what we decided on.


*.DS_Store
*local.meta
*.csv
*.pyo
*.idea
!<some_static_lookup>.csv

  • .csv - is ignored if any search are generating lookups
  • .pyo - any pythongenerated files
  • local.meta - since this is updated by deployment server
  • !.csv - include any static lookups
  • .idea- since we work on macs
  • DS_Store - since we work on macs

Hope this helps

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  &#x1f680; Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...