From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>
Cc: "pdm-devel" <pdm-devel-bounces@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager 2/5] server: api: add support to optionally delete token from remote
Date: Tue, 09 Dec 2025 14:37:20 +0100 [thread overview]
Message-ID: <DETQ66SRJ5E3.18CPDQIGD308D@proxmox.com> (raw)
In-Reply-To: <DETOTZLT0XAZ.17GXCPJPSP7PL@proxmox.com>
On Tue Dec 9, 2025 at 1:34 PM CET, Michael Köppl wrote:
> On Fri Dec 5, 2025 at 7:04 PM CET, Shan Shaji wrote:
>> Previously, when removing a remote, the token was still present in the
>> remote configuration. When users tried to add the remote again, they
>> received an error because a token with the same name already existed.
>> To support deleting the token from the remote, add an optional
>> parameter to the API endpoint.
>>
>> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
>> ---
>> server/src/api/remotes.rs | 45 +++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 43 insertions(+), 2 deletions(-)
>>
>> diff --git a/server/src/api/remotes.rs b/server/src/api/remotes.rs
>> index 298ad13..9f9786c 100644
>> --- a/server/src/api/remotes.rs
>> +++ b/server/src/api/remotes.rs
>> @@ -27,6 +27,7 @@ use crate::api::remote_updates;
>> use crate::metric_collection;
>> use crate::{connection, pbs_client};
>>
>> +use super::pbs;
>> use super::pve;
>> use super::rrd_common;
>> use super::rrd_common::DataPoint;
>> @@ -292,16 +293,56 @@ pub fn update_remote(
>> input: {
>> properties: {
>> id: { schema: REMOTE_ID_SCHEMA },
>> + "delete-token": {
>> + type: bool,
>> + description: "Optional boolean value to delete the token from remote.",
>> + optional: true,
>> + }
>> },
>> },
>> access: {
>> permission: &Permission::Privilege(&["resource"], PRIV_RESOURCE_MODIFY, false),
>> },
>> )]
>> -/// List all the remotes this instance is managing.
>> -pub fn remove_remote(id: String) -> Result<(), Error> {
>> +/// Remove a remote that this instance is managing.
>> +pub async fn remove_remote(id: String, delete_token: Option<bool>) -> Result<(), Error> {
>> let (mut remotes, _) = pdm_config::remotes::config()?;
>
> Isn't that a bit racy, though, considering you're making asynchronous
> network calls if delete_token is true? By the time you arrive at the
> save_config(...) call, the list of remotes you fetched here might have
> changed because another call to remove a remote was made pretty much at
> the same time, causing you to overwrite those changes with the list of
> remotes you fetched here. Not too familiar with the code here, but we
> use pdm_config::remotes::lock_config()?; in other parts to avoid this,
> it seems.
You are right. There is a possibility of race condition. thanks
for pointing it out. I will lock the config here.
>>
>> + if delete_token.unwrap_or(false) {
>> + let remote = remotes
>> + .get_mut(&id)
>
> nit: .get(&id) should be sufficient
Thanks! Will update it.
>> + .ok_or_else(|| http_err!(NOT_FOUND, "no such remote {id:?}"))?;
>> +
>> + let user = remote.authid.user();
>> +
>> + let short_delete_err = |err: proxmox_client::Error| {
>> + format_err!("error deleting token: {}", err.source().unwrap_or(&err))
>> + };
>> +
>> + let token_name = remote
>> + .authid
>> + .tokenname()
>> + .ok_or_else(|| format_err!("Unable to find the token for the remote {}", id))?;
>> +
>> + // connect to remote and delete the already existing token.
>> + match remote.ty {
>> + RemoteType::Pve => {
>> + let client = pve::connect_or_login(&remote).await?;
>
> nit: this could just be pve::connect_or_login(remote).await?
Will update it. Thanks!
>> + client
>> + .delete_token(user.as_str(), token_name.as_str())
>> + .await
>> + .map_err(short_delete_err)?
>> + }
>> + RemoteType::Pbs => {
>> + let client = pbs::connect_or_login(&remote).await?;
>
> nit: same here
>
>> + client
>> + .delete_admin_token(&user, token_name.as_str())
>
> nit: same here for user
>
>> + .await
>> + .map_err(short_delete_err)?
>> + }
>> + };
>> + }
>> +
>> if remotes.remove(&id).is_none() {
>> http_bail!(NOT_FOUND, "no such entry {id:?}");
>> }
>
>
>
> _______________________________________________
> pdm-devel mailing list
> pdm-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
_______________________________________________
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-09 13:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 18:04 [pdm-devel] [PATCH datacenter-manager/proxmox 0/6] fix #6914: add option to remove already existing token Shan Shaji
2025-12-05 18:04 ` [pdm-devel] [PATCH datacenter-manager 1/5] server: pbs-client: add delete admin token method Shan Shaji
2025-12-09 9:36 ` Shannon Sterz
2025-12-05 18:04 ` [pdm-devel] [PATCH datacenter-manager 2/5] server: api: add support to optionally delete token from remote Shan Shaji
2025-12-09 9:36 ` Shannon Sterz
2025-12-09 9:54 ` Shan Shaji
2025-12-09 12:34 ` Michael Köppl
2025-12-09 13:37 ` Shan Shaji [this message]
2025-12-05 18:04 ` [pdm-devel] [PATCH datacenter-manager 3/5] pdm-client: accept `delete-token` argument for deleting api token Shan Shaji
2025-12-09 9:36 ` Shannon Sterz
2025-12-09 13:08 ` Michael Köppl
2025-12-05 18:04 ` [pdm-devel] [PATCH datacenter-manager 4/5] cli: client: add `delete-token` option to delete token from remote Shan Shaji
2025-12-09 14:52 ` Michael Köppl
2025-12-09 16:25 ` Shan Shaji
2025-12-05 18:04 ` [pdm-devel] [PATCH datacenter-manager 5/5] fix: ui: add remove confirmation dialog with optional token deletion Shan Shaji
2025-12-09 9:36 ` Shannon Sterz
2025-12-09 10:08 ` Shan Shaji
2025-12-09 13:38 ` Michael Köppl
2025-12-09 13:52 ` Shan Shaji
2025-12-05 18:04 ` [pdm-devel] [PATCH proxmox 1/1] pve-api-types: generate missing `delete_token` method Shan Shaji
2025-12-09 9:37 ` Shannon Sterz
2025-12-09 14:56 ` [pdm-devel] [PATCH datacenter-manager/proxmox 0/6] fix #6914: add option to remove already existing token Michael Köppl
2025-12-09 17:02 ` Shan Shaji
2025-12-10 16:40 ` 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=DETQ66SRJ5E3.18CPDQIGD308D@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=pdm-devel-bounces@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