All Apps and Add-ons

App.conf version is empty on .spl file

dnamal
Explorer

I would like to put my application into Splunkbase. However when I package my app and send it to splunk validator api, I see the following error.

Splunk App packages must contain a default/app.conf file with an [id]or [launcher] stanza using theversionproperty formatted asMajor.Minor.Revision

I see that although I have a version in my app.conf, after downloading it is deleted from there. I added an [id] stanza to make things work but things go tangled.

0 Karma

dnamal
Explorer

Actually deleting all of the local directory worked.

However I have views and data_models on local directory that I need to use it in my app. I moved the views under the default folder and it worked but the data models are disappeared.

xpac
SplunkTrust
SplunkTrust

Can you please share your actual complete app.conf? Did you place it in local or default?

dnamal
Explorer

I placed it on default/app.conf. I added the id stanza because I was not able to pass those validation requirements.

[default]
[id]
version = 1.0.5
name = thundra

[install]
is_configured = 0

[launcher]
version = 1.0.5
description = Full Observability for AWS Lambda from Thundra
author = Thundra

[package]
id = thundra

[ui]
is_visible = 1
label = Thundra App

When I download it after packaging the .spl file shows the version field "version = " that.

Also this is my local/app.conf
[ui]

[launcher]
version =

0 Karma

jconger
Splunk Employee
Splunk Employee

You will need to delete anything in local. You local version of app.conf takes precedence over your default version of app.conf.

dnamal
Explorer

I have deleted it but nothing is changed.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...