Issue #20020 has been reported by Geoff Meakin.
----------------------------------------
Feature #20020: Puppet fail on error
https://projects.puppetlabs.com/issues/20020
* Author: Geoff Meakin
* Status: Unreviewed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version:
* Keywords:
* Branch:
----------------------------------------
When I'm developing puppet modules/manifests, there is a certain class of error
which is very tricky to debug - that is , some resource that doesn't work, and
then subsequently fixes the cause for the reason it didn't work - (meaning it
works next time round). In order to get a perfect-from-zero puppet run, I have
to spend lots of time checking dependencies and recreating scenarios in order
to get the system into the exact state to see why something didn't work before
fixing it.
It would be really helpful to me (reduce my development time immensely) if you
could do this on any resource
foo_resource { "name":
exit_on_error => true
}
So the system would be left in the non-working state and I could see how I
needed to fix it.
--
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.
