"deployer_push_mode = full" in app.conf can cause issues in SHC environments

[jherodsplunkcom]

The following config is in place in .../default/app.conf.

[shclustering]
deployer_push_mode = full

This causes the local folder NOT to be merged into default when pushed to an SHC from a deployer. The intended result of this is not discussed in the docs and does not appear to be needed as there is nothing in the local folder.

The problem that can come from this is that if someone applies this locally on the Deployer to validate and test the app, which is a common practice, then it will cause deployment pushes to adopt the deployer_push_mode of full changing the way the SHC is configured. The result could be configs pushed to the local folder of each SHC member that causes issues when you try to make changes to those settings in the future.

If this is actually intended to be there, it should be discussed in the docs as it is with serverclass.conf for Deployment Servers and not be present in the default configs.

[max-ipinfo]

Thank you for your feedback. I am sorry for only noticing it now.

I will go over the issue in the next few days.

[max-ipinfo]

@jherodsplunkcom We will be changing to merge_to_default in an upcoming release