>> > I'm all for only collection from the environment you're from but there >> > needs >> > to be a way to override this. No matter the environment I still want all >> > my >> > machines monitored by my Nagios instance which happens to be running on >> > the >> > production environment. >> >> I concur with the sentiments and I think the crowd has spoken. I'm >> pretty sure we'll just add a configuration option for this. >> > > We also collect across multiple production instances which have unique > environments. Nagios being one example, but have several other modules > which do the same. > > We keep dev on a different puppet master, so we haven't had issues with > collisions.
So what if we created a configuration item, say 'collection_environments' and had it accept two different options: 'same' and 'all'. The default is up for argument, but 'all' would keep the existing behaviour. 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/CAE4bNTmfw%2BX8gRvud33G9yODk%2BbMgnAecDWomJTtSkjBi42sqg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
