On 06/18/2014 12:56 PM, Trevor Vaughan wrote:
> e) Use the new proposed magic => Woo, it "just works" if *anything* in
> the catalog includes 'firewall'. This way, if I don't want it, I don't
> get it in an intuitive fashion.

FWIW, I can see this happen rather easily with a metaparameter like

  firewall::rule { "whatever":
     lazy => true,
     trigger => Class[firewall],
  }

*but* this will not work for includes (no, not even using the
resource-like declaration syntax) for much the same reason (I believe)
that class parameter overrides cannot work.

Also, Puppet can do this already, we just call it virtual resources. I
do feel though that many module interoperability use cases of the
firewall variety could be solved using a virtual resources based approach.

But this is essentially derailing the thread. If we find that we *do*
want this for classes, we'll have to kiss *some* frog.

-- 
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/53A17E98.6050101%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to