On 22.03.2011 02:53, Nigel Kersten wrote:
The file{} type can do all of the following:
* manage single files
* manage directories
* manage symlinks
* manage recursive file copies
The intersection of all these bits of functionality makes it difficult
to understand exactly what is going on when you're new to Puppet, and
even experienced users often don't know how combining symlinks/content
management is going to work.
How would people feel about at least splitting out these into their own types?
* symlinks
* recursive file copies
The intersection of files and directories isn't that big a deal, but
we could split out directories too if we wanted.
Wouldn't it make more sense to split it into
file/symlink/directory(/{char,block}device/...), and model/manage
recursive copies as "content of a directory"?
Another question is how current "mixed-content" models like the "purge
empty directory and manually add files" pattern used by the various
conf.d include directories interacts with such a change. In the best
case, this would reduce to something like
directory { "/etc/apache2/conf.d":
ensure => present,
content => empty;
}
Another related type would by "tidy", which is "only" a complex kind of
file purging, no?
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
