> This is the world I see, it won't affect everyone though and > theoretically with 1 hour check-ins it will be solved next run. My > fear is more around those that don't run puppet as often.
Oh. I was under the impression most people run Puppet at least every half hour, if not even more often. I'm likely off the target by a few hours though. > So because there was no environment awareness, all resources from all > environments would be sent to PuppetDB with no environment being > marked. As a consequence, no matter what environment you were > collecting from all resources on that PuppetDB instance were thus up > for collection. Without work-arounds (like what Spencer mentioned) you > may potentially collect both test and prod resources (for example) > that represented the same Type/Title combination thus creating a > duplicate resource. Ah. Interestingly enough I never ran into this. Kinda makes me wonder if that's just dumb luck. 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. -- Daniele Sluijters -- 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/0f1f24c2-f5d0-44a3-b955-19a841982e8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
