Issue #8417 has been updated by Gabriel Filion. Status changed from Closed to Re-opened
I'm sorry to re-open this again, but I fail to see how collection by environment can be useful here. The situation here is that resources get exported with --noop regardless of the environment used and thus can have an impact on systems that would collect them. In order for #5239 to be relevant, exported resources would need to be automatically flagged with some special value and singled out when collecting... or just not exported like one would expect out of a no-operation flag. ---------------------------------------- Bug #8417: Exported resources is exporting to the database with --noop flag https://projects.puppetlabs.com/issues/8417#change-95349 * Author: Andrew Thompson * Status: Re-opened * Priority: Normal * Assignee: eric sorenson * Category: exported resources * Target version: * Affected Puppet version: 3.2.3 * Keywords: ntbf * Branch: ---------------------------------------- When I run puppet with the noop flag resources are being exported to the db. I would expect it to simulate the transaction with the db... This is causing things like nagios host resources being creating before the plugins get there, so I get invalid alerts. -Andrew -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
