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
The above code is still correct according to documentation/examples but of course now produces an error when applying: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Letsencrypt::Certonly[LE_redacted_redacted]: has no parameter named 'suppress_cron_output' (file: /etc/puppetlabs/code/environments/production/modules/site_apache/manifests/vhost/user.pp, line: 74) on node host.example.com.
It seems the suppress_cron_output parameter was removed in f6a6a4e in favor of the cron_output parameter which has the suppress option to replace the functionality. Documentation and example code was not updated to reflect these changes.
The text was updated successfully, but these errors were encountered:
treydock
added a commit
to treydock/puppet-letsencrypt
that referenced
this issue
Dec 2, 2022
@cFire The fix is in #303. Not sure how that got missed during the release process. That's the only place I could find a reference to the old parameter.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
The above code is still correct according to documentation/examples but of course now produces an error when applying:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Letsencrypt::Certonly[LE_redacted_redacted]: has no parameter named 'suppress_cron_output' (file: /etc/puppetlabs/code/environments/production/modules/site_apache/manifests/vhost/user.pp, line: 74) on node host.example.com
.It seems the
suppress_cron_output
parameter was removed in f6a6a4e in favor of thecron_output
parameter which has thesuppress
option to replace the functionality. Documentation and example code was not updated to reflect these changes.The text was updated successfully, but these errors were encountered: