system-config

System configuration for OpenStack Infrastructure

Clark Boylan 4346570a0b Fix letsencrypt_self_generate_tokens defaults We set the letsencrypt_self_generate_tokens value to True in testing which means the variable is valid and exists in testing. However, in production this variable isn't set and doesn't ahve a default so we get: The task includes an option with an undefined variable. The error was: 'letsencrypt_self_generate_tokens' is undefined Fix this by setting the default value for this var to False. Also, add it to the README of letsencrypt-request-certs as this is where it is primarily used. Change-Id: I862df6ea3ff7f3a1df2a088b04d230bb618aaa85		2 months ago
..
defaults	Fix letsencrypt_self_generate_tokens defaults	2 months ago
tasks	letsencrypt : don't use staging in the gate	2 months ago
README.rst	Fix letsencrypt_self_generate_tokens defaults	2 months ago

README.rst

Request certificates from letsencrypt

The role requests certificates (or renews expiring certificates, which is fundamentally the same thing) from letsencrypt for a host. This requires the acme.sh tool and driver which should have been installed by the letsencrypt-acme-sh-install role.

This role does not create the certificates. It will request the certificates from letsencrypt and populate the authentication data into the acme_txt_required variable. These values need to be installed and activated on the DNS server by the letsencrypt-install-txt-record role; the letsencrypt-create-certs will then finish the certificate provision process.

Role Variables