Forum: CFEngine Help Subject: Re: cf3 inputs, branching, selectiveness, staying sane Author: jblaine Link to topic: https://cfengine.com/forum/read.php?3,23400,23409#msg-23409
mark Wrote: ------------------------------------------------------- > Geoff, Hi (again) Mark, Not a big deal, but it's Jeff. I'm not sure where Geoff came from. Seems the list archives prior to 2004 were lost? I can't seem to find my few posts from ~1998 :) > Thanks for your interest. A lot of tweets and > comments from you about CFEngine on the list, but > your message seems a bit vague. What kind of > information is it that you are looking for > specifically? By being too specific, one gets answers which solve a specific problem. I was intentionally vague (though really I don't think that I was, given the code examples) in order to hopefully draw out varied approaches that have worked for others for their environments, and not "here's one way to solve specifically the single thing you're trying to do". My large goal is to not end up with a gigantic mess in a single input file. In trying to reach that goal, I am... > - Advice about how to organize information in > files? (not CFEngine specific) ... asking for others to share ideas about how to group and organize CFEngine inputs and the contents of those inputs. > - Help in understanding syntax? (CFEngine > specific) > > What made you want to have two "body common > control" when they are right next to each other? Put most succinctly, I was trying to keep bundlesequence defined where it made sense for my idea. That idea being: Keep promises.cf as stock as possible and define site-specific stuff in site-specific files. A bundlesequence will be site-specific for us. I want to load site_x_inputs.cf That said, that's *specifics*, and I don't even know what my options really are, so would like to hear even that "that's an awful idea, and here's why". Clearly my first idea/option did not pan out. So instead of further forcing my way through things, ending up with something that works but is ultimately bizarre and overly convoluted, I figured I'd ask those who have already figured out some capital 'P' Patterns that work. For the most part, we're all dealing with the same concepts. Surely there is overlap in solutions to be shared. > Were you hoping to put these into different > files? Yes. > Can you explain more about your purpose (and maybe > less about your immediate frustrations ;-)) I thought I had: "I would love to see how others are solving this. I'm not about to go through the pain of migrating from 2.x to 3.x while repeating the same old mistakes made with 2.x. Our 2.x config (working fine!) is a gigantic mess." _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
