From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: superseded: [PATCH 0/8] subscription: add central key pool registry with reissue support
Date: Thu, 7 May 2026 10:38:20 +0200 [thread overview]
Message-ID: <7f937a28-55b7-4cae-b4b6-aabe9235458a@proxmox.com> (raw)
In-Reply-To: <20260507072436.2649563-1-t.lamprecht@proxmox.com>
Am 07.05.26 um 09:23 schrieb Thomas Lamprecht:
> Thomas Lamprecht (8):
> api: subscription cache: ensure max_age=0 forces a fresh fetch
> api types: subscription level: render full names
> subscription: add key pool data model and config layer
> subscription: add key pool and node status API endpoints
> ui: add subscription registry with key pool and node status
> cli: add subscription key pool management subcommands
> docs: add subscription registry chapter
> subscription: add Reissue Key action with pending-reissue queue
>
> cli/client/src/subscriptions.rs | 226 +++-
> docs/index.rst | 1 +
> docs/subscription-registry.rst | 64 +
> lib/pdm-api-types/Cargo.toml | 4 +
> lib/pdm-api-types/src/subscription.rs | 422 +++++-
> lib/pdm-api-types/tests/test_import.rs | 310 +++++
> lib/pdm-client/src/lib.rs | 157 ++-
> lib/pdm-config/src/lib.rs | 1 +
> lib/pdm-config/src/subscriptions.rs | 102 ++
> server/src/api/mod.rs | 2 +
> server/src/api/resources.rs | 13 +-
> server/src/api/subscriptions/mod.rs | 1199 +++++++++++++++++
> server/src/context.rs | 7 +
> ui/src/configuration/mod.rs | 2 +
> ui/src/configuration/subscription_keys.rs | 458 +++++++
> ui/src/configuration/subscription_registry.rs | 791 +++++++++++
> ui/src/dashboard/subscriptions_list.rs | 18 +-
> ui/src/main_menu.rs | 10 +
> 18 files changed, 3751 insertions(+), 36 deletions(-)
> create mode 100644 docs/subscription-registry.rst
> create mode 100644 lib/pdm-api-types/tests/test_import.rs
> create mode 100644 lib/pdm-config/src/subscriptions.rs
> create mode 100644 server/src/api/subscriptions/mod.rs
> create mode 100644 ui/src/configuration/subscription_keys.rs
> create mode 100644 ui/src/configuration/subscription_registry.rs
>
Payed not enough attention here, so v2:
https://lore.proxmox.com/pdm-devel/20260507082943.2749725-1-t.lamprecht@proxmox.com/
prev parent reply other threads:[~2026-05-07 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:17 [PATCH 0/8] subscription: add central key pool registry with reissue support Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 1/8] api: subscription cache: ensure max_age=0 forces a fresh fetch Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 2/8] api types: subscription level: render full names Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 3/8] subscription: add key pool data model and config layer Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 4/8] subscription: add key pool and node status API endpoints Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 5/8] ui: add subscription registry with key pool and node status Thomas Lamprecht
2026-05-07 8:15 ` Lukas Wagner
2026-05-07 8:33 ` Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 6/8] cli: add subscription key pool management subcommands Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 7/8] docs: add subscription registry chapter Thomas Lamprecht
2026-05-07 7:17 ` [PATCH 8/8] subscription: add Reissue Key action with pending-reissue queue Thomas Lamprecht
2026-05-07 7:50 ` Lukas Wagner
2026-05-07 8:38 ` 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=7f937a28-55b7-4cae-b4b6-aabe9235458a@proxmox.com \
--to=t.lamprecht@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