Re: [Puppet Users] RFC: Make file content specification methods consistent.
2010-11-01 06:18:45 GMT
Nigel Kersten <nigel <at> puppetlabs.com> writes: > ----------------------- Ticket description --------------- > > We have four main ways we can specify file content in a file resource. > > The source parameter > The content parameter > The file function > The template function [...] > Here's a terrible suggestion that hopefully inspires a better one. An array > indicates multi-select logic, separation with a colon means concatenate. That is terrible, not least because it makes use of a valid filename component that some platforms (*cough* Macintosh *cough*) have used as a vital part of their path descriptions, and others use routinely. Hint: /etc/environment/default-path and content is now gonna suck. :) > 1a. Use the first source that exists. [...] > Is this so unsatisfactory that we need to add more parameters? I think it could be satisfactory with only a tiny change that will *also* solve another end-user problem we recently saw on the list:(Continue reading)