From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager 0/3] token secret shadow config
Date: Mon, 01 Dec 2025 15:46:33 +0100 [thread overview]
Message-ID: <DEMYMTOP6041.TFBW4JPG91JQ@proxmox.com> (raw)
In-Reply-To: <20251201092941.291325-1-f.gruenbichler@proxmox.com>
On Mon Dec 1, 2025 at 10:29 AM CET, Fabian Grünbichler wrote:
> this patch series splits out token secrets into their own file,
> replacing them with a placeholder value in the regular remotes.cfg
>
> Fabian Grünbichler (3):
> remote config: let save_config take ownership
> remote config: get token secret from shadow file if shadowed
> remote config: shadow token secrets when saving
>
> lib/pdm-api-types/src/remotes.rs | 50 +++++++++++++++++++++
> lib/pdm-config/src/remotes.rs | 76 +++++++++++++++++++++++++++++---
> server/src/api/pve/lxc.rs | 2 +-
> server/src/api/pve/qemu.rs | 2 +-
> server/src/api/remotes.rs | 6 +--
> server/src/connection.rs | 8 +++-
> 6 files changed, 130 insertions(+), 14 deletions(-)
In general, this looks good to me.
Two things came to mind when testing/reviewing this:
- as noted in the individual patch, the token should be removed when
deleting a remote
- I'm not sure it's super elegant to have `token -` even for *new*
remotes. I think it would be much cleaner to make the token field
optional, but I can see how that would be quite a bit more work
(could entail having to use distinct types for the API, the config
file and internal usage) so I guess it can stay as is for now. Maybe
we can see how we could achieve this in a follow-up. Worst case, we
drop the token parameter in the next major release.
With this in mind,
Reviewed-by: Lukas Wagner <l.wagner@proxmox.com>
Tested-by: Lukas Wagner <l.wagner@proxmox.com>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-12-01 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:29 Fabian Grünbichler
2025-12-01 9:29 ` [pdm-devel] [PATCH datacenter-manager 1/3] remote config: let save_config take ownership Fabian Grünbichler
2025-12-01 9:29 ` [pdm-devel] [PATCH datacenter-manager 2/3] remote config: get token secret from shadow file if shadowed Fabian Grünbichler
2025-12-01 9:29 ` [pdm-devel] [PATCH datacenter-manager 3/3] remote config: shadow token secrets when saving Fabian Grünbichler
2025-12-01 14:39 ` Lukas Wagner
2025-12-01 14:46 ` Lukas Wagner [this message]
2025-12-01 16:44 ` [pdm-devel] applied: [PATCH datacenter-manager 0/3] token secret shadow config Thomas Lamprecht
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=DEMYMTOP6041.TFBW4JPG91JQ@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=f.gruenbichler@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