topic Re: Merging apps from deployment server in Deployment Architecture

Merging apps from deployment server?

jotne — Thu, 01 Dec 2022 16:33:08 GMT

Need some help with deploying and merging an app.

We have a deployment server that store apps in following folders:~/etc/deployment-apps/all This is where we have all app going out to all server.~/etc/deployment-apps/spesial This is custom config for one server.

in the all folder we have an app like this: test.app/default/app.conf with the following content;

[ui] is_visible = false

in the spesial folder we have an app like this: test.app/local/app.conf with the following content

[ui] is_visible = true

Serverclass.conf looks like this:

# Send all app to all servers [serverClass:send.to.all.servers] repositoryLocation = $SPLUNK_HOME/deployment-apps/all restartSplunkd = true restartIfNeeded = true issueReload = true whitelist.0 = * [serverClass:send.to.all.servers:app:*] # Send this apps only to server Mars1 [serverClass:send.to.mars1.servers] repositoryLocation = $SPLUNK_HOME/deployment-apps/spesial restartSplunkd = true restartIfNeeded = true issueReload = true whitelist.0 = Mars1 [serverClass:send.to.mars1.servers:app:*]

Problem is that only one test.app are sent out.
I would like that both are sent out and merged inn to one app with both the local and default folder (local will take presidiene)

If I remove one of the apps, the other will be sendt out but not both.

How can I accomplish this (without using external script etc)?

Have read trough the serverclass.conf file without seeing any easy way to solve this.

Re: Merging apps from deployment server

richgalloway — Wed, 30 Nov 2022 20:15:23 GMT

The DS sends out apps in the one designated repository location. The repositoryLocation setting in a server class overides the default location - it does not supplement it. Therefore, only the one app in the one repository location will be deployed to a given server. There is no merger of apps in a DS, although the DS can merge the default and local directories within an app.

If you need to send variations of an app to two or more clients then you must maintain two full instances of the app, either under different names in a single repositoryLocation or under a single name in different repositoryLocations.

Re: Merging apps from deployment server

jotne — Wed, 30 Nov 2022 20:54:32 GMT

I give you Karma even if this does not help (but give me some more understanding of how this works.)

Sad that there are no way to handle this type of merging since we have a rather large setup with many Tennants. Having only one master of the application and the manual config in two separate places would make it easier to maintain upgrade of apps.

We have one master deploy server that do send all apps to several deployment server, that then sends out app to many servers HF/UF etc.