Issue #8417 has been updated by Stefan Schulte.
What about the following suggestion: 1. normal puppet run: resource gets exported and the collecting host will apply the resource 2. noop puppet run: resource gets exported but with the noop metaparameter set. On the collecting node, you will now see the resource but it does not get applied 3. number 1 and 2 can be changed when setting the noop metaparameter on the exported resource, e.g. setting the metaparameter to `noop => false` will lead to the current behaviour: The collecting node will always apply the exported resource ---------------------------------------- Bug #8417: Exported resources is exporting to the database with --noop flag https://projects.puppetlabs.com/issues/8417 Author: Andrew Thompson Status: Unreviewed Priority: Normal Assignee: Category: exported resources Target version: Affected Puppet version: 2.6.4 Keywords: 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
