Hello,
I already got a standard deployment configuration to work, the unix app is deployed to all servers with machineType linux-* by linking etc/apps/unix/ to etc/deployment-apps/unix/. That an updated app on the deployment server is automatically pushed to all clients is ok for me at the moment.
Now I thought about adding special inputs for example, to all server with device-mapper multipathing.
My idea is using a second serverClass entry with a different repositoryLocation. In that repository I delete everything apart from a local/inputs.conf that contains just the additional multipath input.
I would hope that first the machineType unix app is deployed and after that the multipathing unix app gets kind of merged.
Any idea if something like that could work or what is the correct way to deploy multiple slighty different configurations of the same app?
idea serverclass.conf:
[global]
whitelist.0=*
[serverClass:AppsByMachineType]
machineTypes=windows-intel, linux-i686, linux-x86_64, sunos-sun4u
[serverClass:AppsByMachineType:app:unix]
machineTypes=linux-i686, linux-x86_64, sunos-sun4v
stateOnClient=enabled
restartSplunkd=true
[serverClass:AppsByMachineType:app:windows]
machineTypes=windows-intel
stateOnClient=enabled
restartSplunkd=true
[serverClass:multipathing]
whitelist.0 = server1
[serverClass:multipathing:app:unix]
repositoryLocation = $SPLUNK_HOME/etc/deployment-cat/multipathing
whitelist.0 = server1
restartSplunkd = true
stateOnClient=enabled
... View more