From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH access-control/network 0/2] fix #7520: sdn: clean up dangling ACLs on resource deletion
Date: Thu, 7 May 2026 15:03:30 +0200 [thread overview]
Message-ID: <0472cd7e-4610-488c-80db-5b41a2e70c65@proxmox.com> (raw)
In-Reply-To: <20260505142207.2563052-1-d.riley@proxmox.com>
Thanks for the series!
Would it be possible to send a v2 that also includes route-maps and
prefix-lists?
On 5/5/26 4:21 PM, David Riley wrote:
> Add pruning mechanism to clean up orphaned SDN ACL entries by
> comparing the current `running-config` with the newly compiled state
> during `commit_config`.
>
> This ensures state consistency for manual applies via the UI/API
> as well as during the automatic configuration reload on system boot.
> Covers resources tracked in the `running-config`:
> * Zones
> * VNets
> * Fabrics
> * Controllers
>
> Does not cover IPAMs and DNS as these are not staged.
>
>
> pve-network:
>
> David Riley (1):
> fix #7520: sdn: clean up dangling ACLs on resource deletion
>
> src/PVE/Network/SDN.pm | 45 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
>
>
> pve-access-control:
>
> David Riley (1):
> fix #7520: access-control: add SDN ACL cleanup helper
>
> src/PVE/AccessControl.pm | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
>
> Summary over all repositories:
> 2 files changed, 85 insertions(+), 0 deletions(-)
>
prev parent reply other threads:[~2026-05-07 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 14:22 [PATCH access-control/network 0/2] fix #7520: sdn: clean up dangling ACLs on resource deletion David Riley
2026-05-05 14:22 ` [PATCH pve-network 1/2] " David Riley
2026-05-05 14:22 ` [PATCH pve-access-control 2/2] fix #7520: access-control: add SDN ACL cleanup helper David Riley
2026-05-07 13:03 ` Stefan Hanreich [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=0472cd7e-4610-488c-80db-5b41a2e70c65@proxmox.com \
--to=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.