>> Upon reflection, I think it would be wise to control which resources are >> collected strictly via search expressions. I disfavor a configuration >> setting affecting that, because if there were one then it would be likely >> that different modules would be developed with different assumptions about >> the configured behavior. Or to put it a different way, people should not >> need to refer to Puppet's configuration to determine what any given snippet >> of DSL code means. > > I guess the problem such a solution leaves is, that people who really > do want global collection have to litter their code with explicit > environment == '*' clauses. How many people will get affected by this > would be interesting, seems at least 2 people on the response so far. > Any ideas for that?
That said, I shouldn't speak for others. For those who do currently use global resource collection, how would such a solution affect you? And any other thoughts you can think of ... ken. -- 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/CAE4bNTmqSGQa09NBp8RDaLOa%3D_yesH9MVRNh6RbVZq593DT4cw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
