Add-on: Can't upload new version of my add-on to Splunk cloud?

[amirk]

My add-on is tag.gz is created with local folder when I export it

When I extract it it is created with local folder

When I'm trying to upload the add-on tar.gz I get this message

What is the problem?

Thanks in advance,

Amir

[mcmaster]

The "Export" link in add-on builder is for exporting the development environment so that it can be reimported into another development system. If you click "Validate & Package", this will take you to the interface for validating your package (which will upload it to AppInspect) where you can then download a package that has been properly formatted for publishing on Splunkbase.

[richgalloway]

The problem is apps submitted to Splunk Cloud must not have a local folder or a local.meta file.  You need to take steps to remove the local directory from the tarball before uploading it to Splunk Cloud.  That may mean merging local with default or simply deleting local.

As a rule, Splunk apps must never be delivered with a local directory, whether to cloud or on-prem instances.  Doing so risks overwriting custom settings.

[amirk]

Thank you, I understand but isn't it suppose to be automatically? I also got this error after trying to upload version with local deleted

check_for_bin_files
This file has execute permissions for owners, groups, or others. File: metadata/default.meta
This file has execute permissions for owners, groups, or others. File: README/ta_sepio_systems_add_on_for_splunk_settings.conf.spec
This file has execute permissions for owners, groups, or others. File: appserver/static/js/build/3.licenses.txt
This file has execute permissions for owners, groups, or others. File: default/app.conf
This file has execute permissions for owners, groups, or others. File: appserver/static/js/build/1.licenses.txt
And more...

[richgalloway]

Splunk will combine default and local in the package command, but the OP said nothing about that.  Also, the deployment server can perform the merge, but we're not talking about that here.

As for file security, this is another requirement that Splunk does not handle automatically.  The developer has to make sure files have the proper permissions.  The 'execute' bit must be disabled except on executables in /bin and on directories.  NOTE: Windows cannot set permissions correctly so this must be done on Linux or Mac.