Forum: Cfengine Help Subject: bundlesequence and module protocol Author: elwood Link to topic: https://cfengine.com/forum/read.php?3,21208,21208#msg-21208
I know the documented bundlesequence and the actual bundlesequence are different, so I'm talking about the current sequence listed in src/agent.c. Why is commands so far down on the list? Given the module protocol it would seem that commands is one of the few types that needs to be executed as soon as possible. While many parts of a bundle can set classes, only commands (via modules) and vars (afaict) can set variables. Personally, I'd like to stop receiving errors (well, useless output) about non-existent files named "/some/path/$(echo.variable)". The workaround I have to use right now is have my modules emit a special "module_name_has_run" class to use as a guard for anything that uses a variable that is generated by a module. This works, but yuch. Before anybody says anything about how I'm using cfengine (cause I know I'm not "doing it right" ;). I'm using the modules to integrate cfengine into a large unix environment that has grown organically over three decades (some of the more organic bits have worked here that long). I think it would be best for much of this information to originate in cfengine inputs, but cfengine has to work in our environment well, for quite sometime before anybody will let me move important shared configuration into it. Except for the above issue, the module protocol has been a brilliant way to accomplish this integration. p.s. Thank you for not requiring me to setup any external software just to be able to scale your application to 1000 hosts. p.p.s. are issues with the reference manual best submitted as bugs, or as posts to this forum? _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
