Should restarting a Linux host from within a cfengine policy be avoided?

view story

http://stackoverflow.com – Specifically, if cfengine is used to download and install the most recent version of firmware, does some tests to see if a reboot is required, and the results indicate that the machine needs a restart, is this something that can be done from within cfengine or should that practice be avoided? If so, why? My experience with Puppet tells me that stopping a run to reboot could be a Very Bad Thing n certain cases, so I'm wondering if the same limitations apply to cfengine as well. (HowTos)