Forum: CFEngine Help Subject: Re: Deleting extra entries inside config that's built by edit_line(s) Author: terok Link to topic: https://cfengine.com/forum/read.php?3,25689,25713#msg-25713
Diego, > wouldn't it be easier to use edit_defaults => empty? Using the new template > > > > facility in 3.3.0 Easier.. probably initially, yes. But after a while, not so much :) I'll just open up bit more what I'd be dealing with this sort of bundle. - ~100 of config files (which are not yet managed by cfe) - Each file has some deviation on the values, no 2 files have identical settings. - Some have more , some less. - can have identical values in same file, but under different block sections. - These files are dynamic, and values are prone to be changed. I have thought about the 3.3's template, but haven't experimented with it yet. I'm still running 3.2.3. The changes on 3.3 does make this much more manageable compared to the 3.2 templates. If opting for 3.3 templates, I would have to offload pretty much everything to the template, and work out the values there without variable expansion. This, if I'd want to keep the maintenance effort required in par with edit_line. imho it also decreases the readability of what was promised as it's hidden in the template. If it was just a couple of configs, I wouldn't meddle with the edit_line approach, as it's much more complex _to set up_, compared to template / pure file copy. In my mind the template approach just 'doubles the effort' compared to a more generic edit_line bundle. Granted, getting that generic bundle done in first place can cause some gray hairs. I'm just seeing my current edit_line approach as a very useful 'generic' bundle to enforce various config files from arrays (with little modification), without the need to maintain also templates. That's the goal at least. /Tero _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
