Subject: Configuration management for zoo.cfg


We use saltstack, but the problem is the same for any configuration
management tool like puppet, ansible, etc. We have a zoo.cfg which
contains a like like:

dynamicConfigFile=/usr/local/etc/zookeeper/zoo.cfg.dynamic
However, when zookeeper runs, it changes that line dynamically to

dynamicConfigFile=/usr/local/etc/zookeeper/zoo.cfg.dynamic.100000000
This is a problem since our configuration management tool keeps trying
to put that file back to the "correct" state.

I don't understand why the dynamic list of hosts has to be renamed. Is
there any way to disable that behaviour?
Thanks

Ari