In previous implementations, and this is going back to v2, application maintainers were part of the Cfengine process but separated from Cfengine policies. In these cases, these folks were able to check in and promote configuration files and the system administrators would write Cfengine policy to allow deployment. In practise the policy rarely had to be changed. Typically the agent runs as root, thus convention prevents application support or developers from being aloud to directly alter Cfengine policies. I believe that there is a way to do this now but, I have not done it myself nor have I seen any working examples of such.
Cf v2 example: http://watson-wilson.ca/blog/cfcookbook.html#SECTION00060000000000000000 Sincerely, -- Neil Watson 416-673-3465
CONFIDENTIALITY WARNING This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confidential information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à laquelle il s’adresse et peut contenir de l’information personnelle ou confidentielle. Si le lecteur de ce message n’en est pas le destinataire, nous l’avisons par la présente que toute diffusion, distribution, reproduction ou utilisation de son contenu est strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimez ce message ainsi que toutes les pièces jointes.
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
