On 02/27/2015 06:22 PM, Trevor Vaughan wrote:
> I still can't come up with a scenario where this would ever be an issue.
>
> Auto-creating a resource (especially a directory) is a greater level
> of spooky action at a distance since it's actually *doing* something
> to your system and I'm very against that when possible. (It also
> bloats your catalog, but that's not as much of an issue).

I don't agree. You are not changing the system, you are changing
Puppet's behavior (towards being more consistent, I believe).

Another contrived example of an issue that could arise:

user { 'apprunner':
    home => '/opt/vendor/main-app',
}

file { '/opt': owner => 'sysadmin' }

user { 'sysadmin': require => User['apprunner'] }

Yes, unlikely that such a require would be used. It might emerge from
class interdependencies, though, as part of a larger cycle.

Cheers,
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 puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/54F36D7C.7060605%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to