On 31.03.2014 21: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 ...

ken.


For me simply having the environment as a variable that I'm able to search on is solution enough. The current situation that I have is that I have 2 puppet masters that I'd like to be able to use the same PuppetDB instance. I use Hiera to control deployments and have the simple configuration:

puppet::agent::puppet_server::_nodequery:
  query: 'Class[puppet::master]'
  fact: 'fqdn'

in my common.yaml file to pull out the FQDN of the node defined with the puppet::master class. I would love to be able to update the query to include the environment and be able to have both environments use the same instance. As I deploy the ssh known_hosts via exported resources and all the nodes regardless of which environment would be nice to have realized on all hosts within my network, I wouldn't care about the environment those resources are associated with as they are part of my larger domain as a whole.

--
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/683c2d1b809296372bb4ddb1438ab4ae%40undergrid.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to