Dan, besides philosophy, there are daily practical needs. My daily practical needs require an instrument which allows to push specific changes quickly. I don't need to run the whole set of promises in those moments, it would be just the waste of time and cpu cycles. I find it pretty stupid to write separate set of scripts for urgent maintenance and maintain the Cfengine configuration at the same time to ensure convergence. From my point of view, there must be a single point where I need to define changes, otherwise losing convergence between multiple definition points is just a matter of time. That's why I'm trying to find a solution which could allow me to fit my needs. How far does it affect you? Is there a real problem? If you don't need it, just don't use it.
Besides, there's no shift neither in philosophy, nor in technology indeed. There's cf-runagent already, I just want it to be more effiicient, that's it. There's no security concern here since one can't invoke arbitrary command remotely, just run some predefined bundle. Moreover, the range of possible bundles to run can be narrowed to the initial bundlesequence which could have been applied without cf-runagent's intervention, if one is really afraid of mistakenly running a bundle not intended to be applied to the target host. 2010/11/27 Daniel V. Klein <d...@lonewolf.com>: > The problem that I see with this is that it turns Cfengine into more of a > "push" technology. By defining a class, you're still letting the remote > agent set the policy, but by saying "run this bundle", you're bordering on > setting the policy remotely... > > -Dan > > On Nov 26, 2010, at 6:29 PM, no-re...@cfengine.com wrote: > >> Forum: Cfengine Help >> Subject: Re: what if cf-runagent could be able to call just one bundle from >> the bundlesequence? >> Author: neilhwatson >> Link to topic: https://cfengine.com/forum/read.php?3,19442,19444#msg-19444 >> >> Could be useful. Can you think of any cases where calling a single bundle >> might cause problem? >> >> _______________________________________________ >> Help-cfengine mailing list >> Help-cfengine@cfengine.org >> https://cfengine.org/mailman/listinfo/help-cfengine > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > -- SY, Seva Gluschenko. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
