I created an "app" on my old deployment server in `etc/deployment-apps/` called deployserver, and in it, created the local directory, and in that created deploymentclient.conf. Deploymentclient.conf contains
[deployment-client]
disabled = false
[targer-broker: deploymentServer]
targerUri = newdeployserver.domain.com:8089
[license]
Master_uri = newlicenseserver.domain.com:8089
And when I reload my legacy deployment server, the deployserver app is dropped onto the client. I'm manually restarting the splunkforwarder on the client (something's weird w/ my serverclasses.conf), and when the client comes back up, the new deployment server doesn't see it. Only after I run `bin/splunk set deploy-poll newdeployserver.domain.com:8089` and restart, the splunkforwarder does start talking to the new deployment server.
Reading about precedence, I see that `etc/system/local/` will take precedence over an app config, but I thought the deployment config app was a possibility.
Has anyone done this, created a deployment server app? How'd you get it to work?
Thanks for any help.
↧