On 2014-04-01 03:43, Ken Barber wrote:
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 ...
In my mind there are two big use-cases that are covered by
environments: keeping systems with the same code but different arguments
separate and keeping systems with different code separate. The latter
does not work at the moment due to fundamental problems within the
puppetmaster (global loading of custom types (fixable, but hard, I
understand), and cross-environment differences in the structure of
collected resources (not fixable)).
Therefore I would love to see puppetlabs officially denounce running
structurally differing environments on the same puppetmaster (or create
stronger borders, although I'm worried about the practical side of
this). This allows a default collection across environments without
remorse and will keep the syntax clean.
Generic modules will have to expose a explicit tag/scope parameter for
internally used exported resources anyways, to allow for different use
cases.
Regards, David
--
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/8b316d9cccf769812a74d84cf6a7a498%40hosting.edv-bus.at.
For more options, visit https://groups.google.com/d/optout.
