Issue #22284 has been updated by Andrew Parker. Status changed from Unreviewed to Accepted
The specific use case mentioned in IRC was around converting deprecation warnings into errors. So if we decide to change all warnings into errors, those will need to be included as well. A naive patch of the system wouldn't achieve that since `deprecation_warning` limits its calls to `warn` and so would hide uses of deprecated functionality if `deprecation_warning` itself didn't also handle this behavior switch. A side effect of doing this is that I think we would want to do a quick audit of the codebase to make sure that we use warning consistently. ---------------------------------------- Feature #22284: ability to promote warnings into fails https://projects.puppetlabs.com/issues/22284#change-96753 * Author: Joshua Hoblitt * Status: Accepted * Priority: Normal * Assignee: * Category: compiler * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- As suggested on #puppet-dev this morning by @zaphod42. It would be useful for testing, particularly with CI, to be able to set either a `puppet.conf` parameter and/or a commandline flag that will promote all `warning()` calls to `fail()` calls. This would be analagous to `gcc`'s `-Werror` flag. -- 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.
