On 10/7/10 8:25 AM, "no-re...@cfengine.com" <no-re...@cfengine.com> wrote: > I agree. > > I'm currently pointing all master policy servers for all environments at the > same point in my SVN tree. The only way for me to apply a policy on "DEV" or > "STG" environments would be to modify the classes in the policies themselves. > > We want to be able to write a policy, test it, and be hands off. Then tweak > where that policy gets applied to through some external method.
Why not point different environments at different tags, branches, whatever? Then your revision control system is your "external method" by which you control where a policy is applied. Similar to what's detailed here (though you might do it slightly differently based upon your needs): http://sial.org/howto/cfengine/repository/ This has been pointed to many times on this list, and was written when cf2 was all the rage...but applies equally well to cf3/whatever. -- Mike Hoskins : micho...@cisco.com : +1 (415) 506-UNIX (8649) He knows not how to know who knows not also how to unknow. -- Sir Richard Burton _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
