Issue #8417 has been updated by micah -.
I agree. This feels like it violates the Rule of Least Surprise. Although I see the interesting upgrade bootstrap case for puppetdb, that sounds like using a misfeature as a hack to do something useful at the expense of doing something non-obvious. If a user choses an option flag that seems to be clear that it doesn't do anything, but really it does, then that option flag should not be called 'noop' and instead be more clearly named. I have no good suggestion as 'notreallynoop' seems silly. ---------------------------------------- Bug #8417: Exported resources is exporting to the database with --noop flag https://projects.puppetlabs.com/issues/8417#change-91052 * Author: Andrew Thompson * Status: Re-opened * Priority: Normal * Assignee: eric sorenson * Category: exported resources * Target version: * Affected Puppet version: 2.6.4 * 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
