Open arthurzenika opened 3 years ago
This might just be a documentation bug, the renew hook might be automatic with certbot plugins.
@arthurlogilab I agree it's a documentation error. I'm using
letsencrypt:
config:
deploy-hook = systemctl reload nginx
successfully
I was just hit with this and should someone not update the piller.example? or maybe fix the state so that it puts what you put in post_renew in renewal-hooks ? following the example currently creates a broken setup IF you are using use_package: True
Your setup
Formula commit hash / release tag
git hash : df1b31e72e14ecbeab11bfe728117b7ed9bbacb0
Pillar / config used
Bug details
Describe the bug
post_renew
is documented in pillar.example, but seems only used inletsencrypt/files/renew_letsencrypt_cert.sh.jinja
which is not deployed whenuse_package: True
(default) is used.Expected behaviour
Deploy hooks
Attempts to fix the bug
Not yet
Additional context