Issue #8417 has been updated by eric sorenson. Status changed from Re-opened to Closed
Just had a blinding flash of the obvious here, please correct me if I've gotten this wrong. Storing the exported resources in the database is a byproduct of compiling the catalog, not the agent checking in. If you compile catalogs ahead of time, there's no way of knowing whether the agent will be checking in with `--noop` or not. Since Puppet (and the world in general) is moving to decoupled/asynchronous operations this bug seems like it's not-to-be-fixed. Seems like it would be much higher value to fix #5239 and make exported resources environment-aware; that way you could really separate/hide nodes that were not supposed to be collected . ---------------------------------------- Bug #8417: Exported resources is exporting to the database with --noop flag https://projects.puppetlabs.com/issues/8417#change-95042 * Author: Andrew Thompson * Status: Closed * 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.
