Issue #3933 has been updated by Richard Crowley.
Would having or not having this feature most effectively encourage manifest authors to get dependencies right? I've encountered several Puppet deployments that talk about Puppet "converging" because dependencies weren't all met at the proper time on the first X runs. I can imagine `--failfast` being a useful tool in development but I can also imagine its abuse in a production environment that just runs `puppet agent --failfast` in a `for` loop. Does anyone have a better sense of whether this is a worthwhile consideration? ---------------------------------------- Feature #3933: Option to make Puppet fail as soon as a resource fails. http://projects.puppetlabs.com/issues/3933 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Category: plumbing Target version: Affected version: 0.25.4 Keywords: Branch: I think I might have filed this before on the old trac system, but I can't find it. Basically I'd like the equivalent of bash "set -e" on Puppet client runs. When you're debugging weird transient failures, it would be a lot faster if you could just make puppetd die as soon as a resource failed. -- 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.
