On Fri, May 23, 2014 at 2:58 AM, Paul Seymour <paul.seym...@ig.com> wrote:
> >> +1 - let's file a bug report. >> > > https://tickets.puppetlabs.com/browse/PUP-2650 > For more context here, puppet has a 'deprecation_warning' method which is used for this new message and also in a number of other places. In puppet 3.7, we're planning to introduce a number of additional deprecation messages (for functionality which will be removed in puppet 4) So there are at least two possibilities here: 1) Make all deprecation messages Info-level rather than Warning-level. So you'd need to specify --verbose to see the deprecation messages. 2) Leave the deprecation messages at Warning-level, but add a 'warn-on-deprecation' setting (possibly with a better name). In either case, you'd need to flip a setting to see the deprecation messages (whereas they are in your face today). The downside to (1) is that the deprecation messages would be mixed in with other Info messages that might not be of interest to the person planning their migration to puppet 4. The downside to (2) is it's Yet Another Setting and as such it might not be used as much (i.e. puppet 4 might take more people by surprise). Thoughts? Kylo -- 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/CALsUZFEb9%3DF4vXxc9O6E%3D_agzjuNi_sOgx0P2W-y1C0xA1KHXA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
