|
I'm setting up a deployment server. From what I understand, the deployment server only adds or updates app files and doesn't delete them. Is it "better" to delete the apps we don't want to use, or just disable them? It seems like it would be more efficient to delete the directories for smaller deployment bundles (and in theory quicker updates) and less disk footprint. |
|
I feel like deleting is the cleaner approach, however there is a downside if you are talking about pre-distributed apps (like We do this with the deployment process by creating a dummy (empty) application that contains only the
This way the app is removed initially, and if an upgrade occurs, at least the app does not get enabled again. Of course, I kind of liked the 3.x model for this slightly better, where one app could actually disable another app, but I also see how that could create other problems. At the moment, I think this is the "best" approach. BTW, thanks to gkanapathy for pointing out this idea to me in the first place: http://www.splunk.com/support/forum:SplunkAdministration/4172 |
|
Deployment Server synchronizes entire app folder contents by adding, deleting, or otherwise changing, and it will also remove apps that were removed from Deployment Server configuration. It doesn't matter very much whether you delete or disable apps, your preference. |
