On Thu, May 29, 2014 at 11:30 AM, Kylo Ginsberg <k...@puppetlabs.com> wrote:
> 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? > I'd like the ability to turn off individual deprecation warnings, like a lint check would allow doing. For example, every time I run puppet 3.6.1 right now I get warnings about setting manifest and module path, because we've not moved to directory environments yet. I've read enough people say they're having weird issues about directory environments that I'm going to hold off a few weeks and see how things go. I don't want to disable all deprecation warnings, because if I do something new that triggers a different one, I want to know. -- 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/CADg-rOWdmTcFOKbRN0h-Nw0wenZ9Q1H469H0YBGWPJ0N0wUkNw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
