public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Manuel Federanko" <m.federanko@proxmox.com>,
	<pbs-devel@lists.proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH proxmox-backup 6/7] acme: fix #6372 implement ARI renewal information fetching.
Date: Mon, 27 Jul 2026 15:31:17 +0200	[thread overview]
Message-ID: <DK9E2UIOGKUW.3N7DVUT9RFMWA@proxmox.com> (raw)
In-Reply-To: <20260625141337.181684-7-m.federanko@proxmox.com>

On Thu Jun 25, 2026 at 4:13 PM CEST, Manuel Federanko wrote:
> Try to fetch ARI renewal information and renew based on that, if it is
> not available fall back to normal lifetime based renewal logic.
>
> The ARI check needs to talk to the server, move all checks into the
> worker process and unconditionally call the worker process from all
> entry points.
>
> Add a method that returns the ARI ID from the CertInfo struct, which is
> easier than trying to pass along other information or switching to
> proxmox-acme-api's CertificateInfo struct.
>
> Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=6372
> Signed-off-by: Manuel Federanko <m.federanko@proxmox.com>
> ---
>  src/api2/node/certificates.rs          | 106 +++++++++++++++++++------
>  src/bin/proxmox-daily-update.rs        |   6 --
>  src/bin/proxmox_backup_manager/acme.rs |   8 --
>  3 files changed, 81 insertions(+), 39 deletions(-)
>
[snip]
> diff --git a/src/bin/proxmox_backup_manager/acme.rs b/src/bin/proxmox_backup_manager/acme.rs
> index ed9e5868c..ea14cfe2b 100644
> --- a/src/bin/proxmox_backup_manager/acme.rs
> +++ b/src/bin/proxmox_backup_manager/acme.rs
> @@ -413,14 +413,6 @@ pub fn plugin_cli() -> CommandLineInterface {
>  )]
>  /// Order a new ACME certificate.
>  async fn order_acme_cert(param: Value, rpcenv: &mut dyn RpcEnvironment) -> Result<(), Error> {
> -    if !param["force"].as_bool().unwrap_or(false) {
> -        let (expires_soon, lead_days) = api2::node::certificates::check_renewal_needed()?;
> -        if !expires_soon {
> -            println!("Certificate does not expire within the next {lead_days} days, not renewing.");
> -            return Ok(());
> -        }
> -    }
> -

Hi, Since this was now removed, we no longer get console feedback If the
certificate doesn't expire soon. However, the status was visible inside the
task log. Would showing it in the console as well be a good UX?  

>      let info = &api2::node::certificates::API_METHOD_RENEW_ACME_CERT;
>      let result = match info.handler {
>          ApiHandler::Sync(handler) => (handler)(param, info, rpcenv)?,
> --
> 2.47.3





  reply	other threads:[~2026-07-27 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 14:13 [PATCH proxmox{,-backup,-datacenter-manager} 0/7] acme: fix #6372 implement basic ARI support Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 1/7] acme: client: add methods to fetch renewal information Manuel Federanko
2026-07-24 11:16   ` Shan Shaji
2026-06-25 14:13 ` [PATCH proxmox 2/7] acme: add retry-after header to " Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 3/7] acme: allow specifying the certificate that is replaced by an order Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 4/7] acme: cert: add dedicated ari_id field to the certificate info Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox-backup 5/7] acme: add ari_id to cert info Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox-backup 6/7] acme: fix #6372 implement ARI renewal information fetching Manuel Federanko
2026-07-27 13:31   ` Shan Shaji [this message]
2026-06-25 14:13 ` [PATCH proxmox-datacenter-manager 7/7] acme: fix #6372 use ARI for renewal if available Manuel Federanko
2026-07-27 16:15 ` [PATCH proxmox{,-backup,-datacenter-manager} 0/7] acme: fix #6372 implement basic ARI support Shan Shaji

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=DK9E2UIOGKUW.3N7DVUT9RFMWA@proxmox.com \
    --to=s.shaji@proxmox.com \
    --cc=m.federanko@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=pdm-devel@lists.proxmox.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal