On Wed, May 28, 2014 at 1:53 PM, Andy Parker <a...@puppetlabs.com> wrote:
> On Tue, May 27, 2014 at 11:33 AM, Kylo Ginsberg <k...@puppetlabs.com> > wrote: > >> On Tue, May 27, 2014 at 7:16 AM, Chuck <cssc...@gmail.com> wrote: >> >>> The ability to turn off the deprecation messages would be great. The >>> only things these messages provide are a drain on logging resources, noise >>> in the logs, and confusion from end users. >>> >>> Seems like we have consensus on an ignore-deprecation-warnings setting, >> which defaults to false. >> >> > I think a 'deprecation-level' setting might be more in keeping with > logging. It defaults to warn, but can be turned down to debug if you don't > want to normally see them. > > This seems like it might cause some confusion if users are grepping their logs and not sure if the deprecations are warning/info/debug? I'm more familiar with the model of enabling/disabling a class of warnings (a la gcc or linters, etc). But I have no strong feelings here other than wanting to get this addressed in 3.6.2. Anyone else care to weigh in? -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CALsUZFHyt4UvcNKk0W5L1eZnN2h_qVT3UEF_muQPNz4xyH%2B3hw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
