You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
puppetserver 7.16 logs a deprecation warning with a broken URL:
2024-03-11T17:43:29.958-05:00 WARN [qtp1601237113-43] [puppetserver] Puppet The function 'hiera' is deprecated in favor of using 'lookup'. See https://puppet.com/docs/puppet/7.29/deprecated_language.html (file & line not available)
Expected Behavior
It's very handy that the puppetserver produces a log message with a "go here to learn more" URL. The only thing that needs to change is for the URL it logs to be updated for the current location.
Steps to Reproduce
Steps to reproduce the behavior:
Use hiera() instead of lookup() somewhere in your puppet code
restart puppetserver on your puppet server.
Do a 'no-op' puppet agent run
browse the /var/log/puppetlabs/puppsetserver/puppetserver.log
copy the URL and paste it into a browser
puppet.com's custom 404 page comes up
Environment
Version: puppetserver 7.16.0, puppet-agent 7.29.1
Platform: RHEL 9.x
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! I've looked a bit into it and found the warning is coming from the Puppet code base itself. I've opened a related ticket here that you can track its progress puppetlabs/puppet#9378
Describe the Bug
puppetserver 7.16 logs a deprecation warning with a broken URL:
2024-03-11T17:43:29.958-05:00 WARN [qtp1601237113-43] [puppetserver] Puppet The function 'hiera' is deprecated in favor of using 'lookup'. See https://puppet.com/docs/puppet/7.29/deprecated_language.html (file & line not available)
Expected Behavior
It's very handy that the puppetserver produces a log message with a "go here to learn more" URL. The only thing that needs to change is for the URL it logs to be updated for the current location.
Steps to Reproduce
Steps to reproduce the behavior:
Environment
The text was updated successfully, but these errors were encountered: