Ahoy puppet-devs, So I've recently noticed the deprecation notices for the validate_* and is_* functions withing stdlib. As a consumer of the stdlib who currently needs to continue to support puppet 3 and hasn't moved to puppet 4 typing for ~40 modules, this is a giant pain. Additionally we do not require (nor leverage) any of the old edge cases that are trying to continue to be maintained under the validate_legacy function. Is there a reason we can't just keep these is_* and validate_* functions as is without the deprecation and/or just fix these in a newer version of stdlib? Is there some additional info as to why this decision was made? Having to go through our modules and switch out to the validate_legacy functions is an effort we don't have the resources to undertake and the deprecation notices aren't something we can live with as they make it very hard to figure out when something actually breaks.
Additionally I'd like to point out that the deprecation notices make it next to impossible to figure out what is deprecated, see http://logs.openstack.org/89/388589/1/gate/gate-puppet-openstack-integration-4-scenario001-tempest-centos-7/fc2567b/console.html#_2016-10-19_22_24_59_667975 Thanks, -Alex -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/79755ecd-c0e0-442f-ae7e-05fb4c1575ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
