RE: [Puppet Users] Re: RFC: Splitting up the file{} type functionality.

[Jennings, Jared L CTR USAF AFMC 46 SK/CCI]

jcbollinger:
> On the other hand, perhaps the new thing needed is something
> different: what about resource sub-types? [...]
> plainfile { "/etc/profile.d/foo.sh": source => "..." }
> filelink { "/etc/profile.d/foo.sh": target => "/opt/foo/foo_env.sh" }
> service { "foo": require => File["/etc/profile.d/foo.sh"] }
...
> it models the problem domain better

This is an excellent idea. It breaks the exact correspondence between
file/File, service/Service, etc., but that's easier to explain than
symlinks and recursion (if not easier to implement).

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.