<!--
Thank you for contributing to this project!
-->
On FreeBSD and OpenBSD gid 0 is 'wheel', not 'root' and it will fail.
Using gid 0 corrects this simply.
I didn't find an issue for this, but the PR #231 is similar.
Allow specifying which key type to generate. Certbot changed it's default from rsa to elliptic curve, but I kept the default to rsa for backwards compatibility.
<!--
Thank you for contributing to this project!
-->
Add dns-ovh support based on dns_rfc2136 implementation
Fixes #63.
We rename the environment
to venv_vars
in order to ensure that hiera calls do not break, as soon as a puppet execution flow enters our module. For consistency's sake, we change environment
not only in the main class (where it's definitely needed: rodjek/puppet-lint#574), but also in the certonly
define.
Change the random seed per hour for letsencrypt::certonly
cronjob resource.
Fixes #47
This PR aims at removing the system cron or systemd timer when the renew cron is managed by puppet (this doesn't handle certonly cron). If we don't do that on certains distro (for exemple Debian), a cron will be automaticaly added by the package and might renew the certificate before the puppet cron, and thus the puppet renew hooks won't be executed.
Fixes #164
modulesync 5.4.0
Add dns-azure to list of allowed plugins.
This is one of the 3rd party plugins listed at https://eff-certbot.readthedocs.io/en/stable/using.html#third-party-plugins
I'm currently using this module on my branch on a RHEL 9 host, but the only caveat is the fastest way I found to get the plugin working was via the snap package:
```puppet
include snap
package { 'certbot':
ensure => installed,
provider => 'snap',
install_options => ['classic'],
}
file { '/usr/bin/certbot':
ensure => link,
source => '/snap/bin/certbot',
require => Package['certbot'],
}
package { 'certbot-dns-azure':
ensure => installed,
provider => 'snap',
install_options => ['channel=edge'],
require => Package['certbot'],
}
```
And also had to run snap set certbot trust-plugin-with-root=ok
before the last package resource, but didn't take the time yet to examine what changed on disk in order to create an exec resource to do that.
<!--
Thank you for contributing to this project!
-->
This PR makes sure that only single certificate can be processed at the same time. Make sure to obtain exclusive lock before executing renewal command.
flock
command is used to obtain exclusive lock (with 30 seconds timeout).
Resolve errors like this, when randomized cron job time is not enough:
Another instance of Certbot is already running.
My apologies on missing this. In testing https://github.com/voxpupuli/puppet-letsencrypt/pull/254 I had manually enable the python36 module stream at some point before hand, but after running on a fresh install I realized certbot requires this module stream to be enabled per:
Error: Execution of '/bin/dnf -d 0 -e 1 -y install certbot' returned 1: Error:
Problem: package certbot-1.20.0-1.el8.noarch requires python3-certbot = 1.20.0-1.el8, but none of the providers can be installed
- package python3-certbot-1.20.0-1.el8.noarch requires /usr/bin/python3.6, but none of the providers can be installed
- conflicting requests
- package python36-3.6.8-2.module_el8.3.0+6191+6b4b10ec.x86_64 is filtered out by modular filtering
Error: /Stage[main]/Letsencrypt::Install/Package[letsencrypt]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/dnf -d 0 -e 1 -y install certbot' returned 1: Error:
Problem: package certbot-1.20.0-1.el8.noarch requires python3-certbot = 1.20.0-1.el8, but none of the providers can be installed
- package python3-certbot-1.20.0-1.el8.noarch requires /usr/bin/python3.6, but none of the providers can be installed
- conflicting requests
- package python36-3.6.8-2.module_el8.3.0+6191+6b4b10ec.x86_64 is filtered out by modular filtering
Fixes #236
<!--
Thank you for contributing to this project!
-->
Adding feature support for the certbot-plugin-gandi created by @obynio
The plugin use the Production API key.
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
N/A
It was strange to me that the module mentions the apache plugin, but has no installation of said plugin anywhere.
In the meantime i used standalone and did an ugly cron pre/post combo But this should address the issue properly