public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, David Riley <d.riley@proxmox.com>
Subject: applied: [PATCH common/manager v3 0/4] fix #8006: acme: lifetime-based certificate renewal threshold
Date: Wed, 28 Oct 2026 18:27:52 +0100	[thread overview]
Message-ID: <179320847229.1870597.16235995289031511910.b4-ty@b4> (raw)
In-Reply-To: <20261021095229.50842-1-d.riley@proxmox.com>

On Wed, 21 Oct 2026 11:52:25 +0200, David Riley wrote:
> Thanks Michael K. for taking a look at v2.
> 
> Differences from v2:
> * Split both pve-common and pve-manager patches into two commits each
>   (4 commits total) as suggested by Michael K.
> 
> Differences from v1:
> * Refactor: Reduce certificate reads by combining the read of
>   notBefore and notAfter.
> * Add: Warning users of certificates with lifetime <= 0
> * Add: minimum lead time of 3 days
> * Update 'force' parameter description in API schema
> * Add: dynamic lead time calculation to bin/pveupdate
> 
> [...]

Applied, thanks!

[pve-common] applied to git/pve-common.git (master)
[1/2] certificate: add helper to extract validity period
      https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=ee8a63829f93fc2e5ff9b330dc2bd097ac273b68
[2/2] certificate: add helper for lifetime-based ACME renewal lead time
      https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=07097f6f24a78d1cbc8839b0b9ae3b46c8198e52

[pve-manager] applied to pve-manager.git (master)
[1/2] fix #8006: api: acme: use lifetime-based certificate renewal lead time
      https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=4ef7f6a03a7f4cc3787adf94340ae33235640e5d
[2/2] fix #8006: pveupdate: use lifetime-based renewal lead time
      https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=5fba1afba8cd2c16724a4b6d74602b01a50e28d9




      parent reply	other threads:[~2026-10-28 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  9:52 [PATCH common/manager v3 0/4] fix #8006: acme: lifetime-based certificate renewal threshold David Riley
2026-10-21  9:52 ` [PATCH pve-common v3 1/4] certificate: add helper to extract validity period David Riley
2026-10-21  9:52 ` [PATCH pve-common v3 2/4] certificate: add helper for lifetime-based ACME renewal lead time David Riley
2026-10-21  9:52 ` [PATCH pve-manager v3 3/4] fix #8006: api: acme: use lifetime-based certificate " David Riley
2026-10-21  9:52 ` [PATCH pve-manager v3 4/4] fix #8006: pveupdate: use lifetime-based " David Riley
2026-10-28 17:27 ` Thomas Lamprecht [this message]

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=179320847229.1870597.16235995289031511910.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=d.riley@proxmox.com \
    --cc=pve-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