Greetings, In https://docs.splunk.com/Documentation/Splunk/8.0.6/Admin/Serverclassconf , the description for serverclass.conf, it details this: [global]
repositoryLocation = <path>
* The repository of applications on the server machine.
* Can be overridden at the serverClass level. It then goes on to describe the serverclass level: [serverClass:<serverClassName>]
* A server class can override all inheritable properties in the [global] stanza.
repositoryLocation = <path> Taking these together, it seems a Deployment Client can only ever receive its apps from one repositoryLocation at a time. Is this correct? If so, bummer. If not, is there a way to set up a Deployment Server to have two repos, say one for inputs, the other for outputs, and have the Client configured like so: [deployment-client]
clientName = apps_from_output_repo.apps_from_inputs_repo In my head each repo would be its own app in the Deployment Server, and each have its own serverclass.conf, but one app would handle the [global] level, the other the [serverClass] level.
... View more