From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Shan Shaji" <s.shaji@proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH datacenter-manager v3 3/6] pdm-client: accept `delete-token` argument for deleting api token
Date: Fri, 13 Feb 2026 14:20:53 +0100 [thread overview]
Message-ID: <DGDV5JUSKOFL.1W9IMRD0PJUKZ@proxmox.com> (raw)
In-Reply-To: <20260211152016.445817-4-s.shaji@proxmox.com>
On Wed Feb 11, 2026 at 4:20 PM CET, Shan Shaji wrote:
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
>
> changes since v2: No changes.
> changes since v1:
> - reformated using `rustfmt`.
> - added doc comment.
>
> lib/pdm-client/src/lib.rs | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/lib/pdm-client/src/lib.rs b/lib/pdm-client/src/lib.rs
> index 01ee6f7..ef534cc 100644
> --- a/lib/pdm-client/src/lib.rs
> +++ b/lib/pdm-client/src/lib.rs
> @@ -136,8 +136,15 @@ impl<T: HttpApiClient> PdmClient<T> {
> Ok(())
> }
>
> - pub async fn delete_remote(&self, remote: &str) -> Result<(), Error> {
> - let path = format!("/api2/extjs/remotes/remote/{remote}");
> + /// Deletes a remote, with optional support to also delete the associated token.
> + pub async fn delete_remote(
> + &self,
> + remote: &str,
> + delete_token: &Option<bool>,
This can just be `Option<bool>`.
In general, passing &Option<T> is often a bit of an antipattern, instead
it's more idiomatic to pass Option<&T>. If the caller has a &Option<T>,
they can always call Option::as_ref to get Option<&T> [1].
In this concrete case here, since `bool` is Copy [2], its best to just use
Option<bool>.
[1] https://doc.rust-lang.org/std/option/enum.Option.html#method.as_ref
[2] https://doc.rust-lang.org/std/marker/trait.Copy.html
> + ) -> Result<(), Error> {
> + let path = ApiPathBuilder::new(format!("/api2/extjs/remotes/remote/{remote}"))
> + .maybe_arg("delete-token", delete_token)
> + .build();
> self.0.delete(&path).await?.nodata()?;
> Ok(())
> }
next prev parent reply other threads:[~2026-02-13 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 15:20 [PATCH datacenter-manager/proxmox v3 0/7] fix #6914: add option to remove already existing token Shan Shaji
2026-02-11 15:20 ` [PATCH datacenter-manager v3 1/6] server: pbs-client: add delete admin token method Shan Shaji
2026-02-13 13:20 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 2/6] server: api: add support to optionally delete token from remote Shan Shaji
2026-02-13 13:20 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 3/6] pdm-client: accept `delete-token` argument for deleting api token Shan Shaji
2026-02-13 13:20 ` Lukas Wagner [this message]
2026-02-11 15:20 ` [PATCH datacenter-manager v3 4/6] cli: client: add `delete-token` option to delete token from remote Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 5/6] fix: ui: add remove confirmation dialog with optional token deletion Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 6/6] cli: admin: add `delete-token` option to delete token from remote Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH proxmox v3 1/1] pve-api-types: generate missing `delete_token` method Shan Shaji
2026-02-13 13:19 ` [PATCH datacenter-manager/proxmox v3 0/7] fix #6914: add option to remove already existing token Lukas Wagner
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=DGDV5JUSKOFL.1W9IMRD0PJUKZ@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.shaji@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