Hi,
thanks for your elaborate design sketch.
Sorry for limiting my quote severely.
On 01/30/2012 06:28 PM, Nick wrote:
> +package { 'libfoo': ensure => present }
Is this different from John's "constraint" proposal?
To me this didn't become clear: Does the manifest still need to declare
an actual package { "libfoo" } somewhere, or is this implied by at least
one assertion regarding any of its parameters?
Of the latter is the case, then this is not different from just allowing
puppet to consume multiple declarations of the same resource, along with
all the oft-discussed difficulties.
If instead, there still is that one central resource declaration
somewhere, I'm pretty sure this is the same as constraints.
Which is probably a really neat idea.
Cheers,
Felix
--
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.
