puppet_stdlib.git - [puppet

Age	Commit message (Collapse)	Author
2016-11-24	Deprecation - Use puppet stacktrace if available	Helen Campbell
	A previous PR (#685) was raised on this issue, however once it was merged it was discovered that Puppet 3 with future parser enabled was calling the Puppet 4 version of the deprecation function. The Puppet stacktrace is not available until Puppet 4.6, so this was breaking existing setups. The solution was to check is the stacktrace was defined, and if it was to use it as part of the message output.
2016-11-21	Revert "Call site output for deprecation warnings"	Bryan Jen

2016-11-21	Call site display for deprecation warnings	Helen Campbell

2016-10-09	Update deprecation() so warnings can be disabled for CI	David Schmitt

2016-10-08	Revert "Addition of logging with file and line numbers"	David Schmitt
	This reverts commit b63862ff43194194f7428739a32cfe13bad1e7ed, as it would only show the irrelevant first entry of the ruby stack trace. The puppetserver log does contain the full trace information, or you can use --strict=error to cause a hard failure when hitting a deprecation. # Conflicts: # lib/puppet/functions/validate_legacy.rb
2016-09-06	Addition of logging with file and line numbers	Helen Campbell

2016-09-05	Deprecation function to be mutable in all cases	Helen Campbell

2016-07-18	(MODULES-3529)add deprecation function	tphoney