Deployment Architecture

Promoting to App level in deployed App

Jason
Motivator

Say I use deployment server to deploy an App (with user interface) to a search head, and a user uses it, creates a search, and promotes it to App level to share with others.

Does this search, now in the App folder for the deployment server-managed App, soon disappear because it makes the App folder have a different checksum than on the deployment server, thus downloading and reinstalling the App (and possibly rebooting the Search Head)?

Something tells me any App deployed to a search head should not allow object promotion into it, unless Splunk handles this magically somehow.

1 Solution

gkanapathy
Splunk Employee
Splunk Employee

Correct, if a deployment server managed app is changed (by promotion, or by changing permissions, or anything) it will be reverted back to the original DS managed version. probably it makes sense to make sure that no-one can create items in DS managed apps, perhaps by putting into metadata/local.meta of the app:

[]
access = write : [] , read : [ * ]

for example.

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

Correct, if a deployment server managed app is changed (by promotion, or by changing permissions, or anything) it will be reverted back to the original DS managed version. probably it makes sense to make sure that no-one can create items in DS managed apps, perhaps by putting into metadata/local.meta of the app:

[]
access = write : [] , read : [ * ]

for example.

Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...