| Puppet Version: 8.0.0
Puppet Server Version: N/A
OS Name/Version: all Puppet 8 now defaults to strict=error despite what the official docs say (I filed PUP-11867). One of the impacts of this is that all warnings become errors. This is particularly problematic for deprecation warnings, since now by default deprecations take place immediately. An example of this is the recent change to puppetlabs/stdlib to namespace all its functions. Using the old function names, e.g. ensure_packages (puppetlabs-stdlib #1365), will now result in an error that terminates the Puppet run. Desired Behavior: Deprecation warnings should, by default, be warnings that don’t block Puppet runs.
Actual Behavior: Deprecations warnings immediately terminate Pupet runs. Example: From a recent CI job on one of my modules:
Error: Evaluation Error: Error while evaluating a Function Call, deprecation. shell_escape. This function is deprecated, please use stdlib::shell_escape instead. at ["/etc/puppetlabs/code/environments/production/modules/rustup/templates/env.sh.epp", 7]:["/etc/puppetlabs/code/environments/production/modules/rustup/manifests/global.pp", 100] (file: /etc/puppetlabs/code/environments/production/modules/rustup/templates/env.sh.epp, line: 7, column: 24) on node 4e706a032afe.hgz2n3xr2b2uteg1gmg5rpevog.jx.internal.cloudapp.net |
|
