Kenyon Ralph

Also, `params.pp` should be eliminated, like what I've done for the APT module in https://github.com/puppetlabs/puppetlabs-apt/pull/1172. This docker module would take a lot more effort though.

Similar report here about the upload case: https://www.jfrog.com/jira/browse/BI-526

@teluq-pbrideau thanks for the clarification. I'm not using this functionality of this module, so this doesn't really affect me, but it seems like it's OK if you have to explicitly...

Pinning to the latest commit also works until there is a release. Example: https://github.com/kenyon/puppet/commit/d13379170314d349eb9a03b602a220c7989bd24a

In case anyone else messes up their system with v8.1.0 of puppetlabs-puppetdb, I was able to recover (on Debian 11) by setting the puppetlabs-puppetdb version to 8.0.1 in `Puppetfile`, doing...

@vchepkov nice, I'd guess the issue is in the changes to the SQL code, I'm assuming the file mode changes are innocuous.

> given the "new" version for the dependency, should this be marked backward-incompatible? I think yes, because users of this module who use it with puppetlabs-apt would need to update...

Same as #1543?

You would override this parameter: https://github.com/saz/puppet-sudo/blob/02ef57320f1c2611adf3b55f42158ad58680f6c0/manifests/init.pp#L122 Example in hiera: ```yaml sudo::package: sudo-sssd ``` Example in puppet code: ```puppet class { 'sudo': package => 'sudo-sssd', } ```