Issue #16907 has been updated by Josh Cooper.
Hi Sandra, one idea would be to validate your manifests before promoting into production, especially if you're putting your manifests in revision control, and which we recommend in case you need to revert a change easily. For validation, you may want to look into puppet-lint <https://github.com/rodjek/puppet-lint> It should be possible to write a plugin to check for your specific concern. ---------------------------------------- Bug #16907: prerun_command option in puppet.conf doesn't work https://projects.puppetlabs.com/issues/16907#change-73132 Author: Sandra Schlichting Status: Needs More Information Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.7.19 Keywords: Branch: If I use puppet.conf as <pre> [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig prerun_command = /bin/false </pre> or <pre> [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl prerun_command = /bin/false [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig </pre> and then on a node do <pre> puppet agent --listen --test --noop </pre> then it doesn't fail, as I would have expected. My purpose for this is to execute a script on the puppetmaster everytime a node tries to connect. -- 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.
