From: Arun Isaac <arunisaac@systemreboot.net>
To: Felix Lechner <felix.lechner@lease-up.com>, 67497@debbugs.gnu.org
Cc: bruno victal <mirai@makinata.eu>
Subject: [bug#67497] [PATCH] Multiple deploy hooks in certbot service
Date: Tue, 28 Nov 2023 00:24:19 +0000 [thread overview]
Message-ID: <874jh6bu8c.fsf@systemreboot.net> (raw)
In-Reply-To: <87zfyzkkt4.fsf@lease-up.com>
Hi Felix,
> Certificates are often used to secure multiple services. It is helpful
> to have separate hooks for each service.
It's already possible to write the deploy-hook as a G-expression
constructed script (using program-file) that invokes multiple hooks in
succession. Something like:
(program-file "deploy-hook"
(with-imported-modules '((guix build utils))
#~(begin
(use-modules (guix build utils))
(invoke "/some/hook")
(invoke "/some/other/hook"))))
Here /some/hook and /some/other/hook can themselves be recursively
constructed using program-file. So, do we really need a service that
explicitly accepts multiple deploy hooks?
Regards,
Arun
next prev parent reply other threads:[~2023-11-28 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zfyzkkt4.fsf@lease-up.com>
2023-11-27 21:20 ` [bug#67497] [PATCH 1/4] In documentation, rename %certbot-deploy-hook back to %nginx-deploy-hook Felix Lechner via Guix-patches via
2023-11-27 21:20 ` [bug#67497] [PATCH 2/4] In certbot documentation, call environment variables by their proper name Felix Lechner via Guix-patches via
2023-12-16 20:58 ` Bruno Victal
2023-11-27 21:20 ` [bug#67497] [PATCH 3/4] In certbot service, reduce code duplication Felix Lechner via Guix-patches via
2023-11-27 21:20 ` [bug#67497] [PATCH 4/4] In certbot's client configuration, offer multiple deploy-hooks Felix Lechner via Guix-patches via
2023-11-28 0:24 ` Arun Isaac [this message]
2023-12-16 20:50 ` [bug#67497] [PATCH] Multiple deploy hooks in certbot service Bruno Victal
2023-12-17 17:46 ` Felix Lechner via Guix-patches via
2023-12-19 6:29 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jh6bu8c.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=67497@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=mirai@makinata.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.