Metadata Valid
No translation
Some Operating Systems (a current OpenBSD release) don't have group 'root' - this PR allows setting the group to something else.
Default of group:root has not changed
N/A
<!--
Thank you for contributing to this project!
-->
I added support to configure environments for the letsencrypt renew cron job. This way it possible to add for example an email address to send the output from the cronjob.
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.
I added automatic installation of the ...-certbot-nginx-... package when 'plugin' => 'nginx' is given to define letsencrypt::certonly. And i provided an example in Readme.
On Centos for example, when a Nginx web server is running, simply asking Certbot to create or renew certificates is not enough. It requires an additional package or plugin,
<!--
Thank you for contributing to this project!
-->
Use the first domain for $cert_name instead of the $title.
This doesn't change anything if $domains is undefined, or if the $title is already the same as the first argument of the list passed to $domains.
certbot CLI by default will use the first domain as the cert-name and path to store the certificate files.
This puppet module should do the same.
(I separated this PR from #219 to allow merging separately, as this could potentially breaks things as it did when the --cert-name $title was introduced in 8f8e4f98)
This also adds support for naming services to restart with systemd instead of long-handing it all.
It also adds support for managing firewalls using firewalld for systems that are not meant to be http/https accessible at all times.
These three are essentially the same support and it is difficult to break it up
Again, I would love help knowing quite how to create the CI acceptances for this.
As referenced in #240 the official installation method was changed
in December 2020, deprecating the use of the certbot-auto script,
and recommending snap as the primary package source.
As snap isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of exec commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.
Since we can no longer use the certbot-auto script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html. Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.
As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.
I've also taken the opportunity to update the version of certbot
that's checked out during VCS installation since 0.39.0 is now
around 1.5 years old. Version 1.7.0 is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
Fixes #240
<!--
Thank you for contributing to this project!
-->
Add dns-ovh support based on dns_rfc2136 implementation
modulesync 4.0.0
Adding feature support for the Certbot DNS Cloudflare plugin.
The plugin itself allows for two types of authentication, API token or Global API Key and corresponding Email so both are supported in this change.
Cloudflare recommends API tokens as they're more secure, so this module will prioritize token authentication over key authentication if both are provided.
n/a
<!--
Thank you for contributing to this project!
-->
When I added a Ubuntu 20.04 node to my puppet master, it could not find the package name for the DNS plugin. This fixed it.
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->