Are there any files that can't be managed with the deployment server?

[responsys_cm]

Are there any config files (other than server.conf perhaps) that cannot be managed with the deployment server? I know that when I make edits in the GUI to the forwarding config, for example, I see the outputs.conf file appear in /opt/splunk/etc/system/local. But if I copy that file to an app in /opt/splunk/etc/apps, it seems to work.

What about files like authorize.conf or authentication.conf? Are there any limitations?

Thx.

Craig

[sbrant_splunk]

It's not individual files that are in or out of scope for deployment server, it's the location where they can be placed. By default, "apps" that are deployed via deployment server will be placed in $SPLUNK_HOME/etc/apps. Deployment server cannot manage configuration files located in SPLUNK_HOME/etc/system/local.

[sbrant_splunk]

I may have misunderstood your question. It's not that deployment server can't drop any configuration file onto a deploymentclient but as you point out, there are some files where it doesn't make sense to manage them via DS. Those are generally configurations that would best be put in $SPLUNK_HOME/etc/system/local, instead of within an app context.

[responsys_cm]

What about files like authentication.conf where Splunk will encrypt the LDAP bind password after the next restart of the server? If I distribute that with the deployment server, I would have to put the unencrypted password in the deployment server config file. When each instance restarts, it'll encrypt that password differently, so the deployment server will then overwrite it...

How can Splunk (or a tool like puppet/flacm/bigfix/etc) distribute and manage a file like that where part of the file will change on each instance?