From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-firewall v2] api: aliases: make 'cidr' optional when updating
Date: Wed, 14 Oct 2026 17:30:08 +0200 [thread overview]
Message-ID: <179199180896.318505.14249674297284436098.b4-review@b4> (raw)
In-Reply-To: <20260929132534.479718-1-a.bied-charreton@proxmox.com>
> @@ -251,7 +251,10 @@ sub register_update_alias {
>
> raise_param_exc({ name => "no such alias" }) if !$aliases->{$name};
>
> - my $data = { name => $param->{name}, cidr => $param->{cidr} };
> + my $data = {
> + name => $param->{name},
> + cidr => $param->{cidr} // $aliases->{$name}->{cidr},
> + };
> $data->{comment} = $param->{comment} if $param->{comment};
The comment here gets overwritten when updating the cidr, also when
renaming.
--
Stefan Hanreich <s.hanreich@proxmox.com>
next prev parent reply other threads:[~2026-10-14 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 13:25 [PATCH pve-firewall v2] api: aliases: make 'cidr' optional when updating Arthur Bied-Charreton
2026-10-14 15:30 ` Stefan Hanreich [this message]
2026-10-15 5:46 ` superseded: " Arthur Bied-Charreton
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=179199180896.318505.14249674297284436098.b4-review@b4 \
--to=s.hanreich@proxmox.com \
--cc=a.bied-charreton@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