Hi,
On 03/28/2014 08:14 PM, Jesse Hathaway wrote:
>
> If you allow the resources file { "/tmp": } and directory {
> "/tmp": } to
> coexists, you are bound to face trouble. Since both represent the same
> file system entry, puppet should handle them with exactly one
> resource.
> It's a sane design in the given domain.
>
>
> That is a problem puppet could alert on, or puppet could just let the
> managed OS tell whether that state is permissible.
I may be missing something, but that can never be a consistent single
state on any platform.
A path will always lead to a file *or* a directory *or* a symlink.
Allowing a directory { } syntax might be conceivable if directory and
link were basically aliases for the file resource type. They would munge
the ensure values differently.
I don't think that would add much value though, because behind the
scenes, they would map back to the file type. To the user, this would
potentially be very confusing. (Also, I sense much opportunity for weird
bugs in the implementation.)
Regards,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/5336E12E.7070803%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.
