From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Sichert <l.sichert@proxmox.com>
Subject: applied: [PATCH manager v3 0/2] ui: fabrics: handle unsupported IP properties for BGP interfaces
Date: Wed, 15 Jul 2026 14:24:04 +0200 [thread overview]
Message-ID: <178411821561.2916317.4171483330747393973.b4-ty@b4> (raw)
In-Reply-To: <20260715081519.29721-1-l.sichert@proxmox.com>
On Wed, 15 Jul 2026 10:15:14 +0200, Lukas Sichert wrote:
> BGP unnumbered interfaces do not support per-interface IPv4 or IPv6
> addresses. The UI already hid the IPv6 column through a declarative
> support flag, but IPv4 needed a protocol-specific initComponent()
> override that manually filtered the base column list.
>
> This series first adjusts the IPv4 column handling to make it optional
> via a declarative support flag. It then uses the IPv4/IPv6 support flags
> to avoid sending unsupported ip/ip6 interface data to the backend.
>
> [...]
Applied, thanks!
[1/2] ui: fabrics: make IPv4 interface column optional
commit: 79fc8f141661dc15f9352a0d00f53faae52eb404
[2/2] ui: fabrics: skip unsupported IP properties on submit
commit: cd09954e2915d60f636dfa8fd3416ca425566bbb
prev parent reply other threads:[~2026-07-15 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:15 [PATCH manager v3 0/2] ui: fabrics: handle unsupported IP properties for BGP interfaces Lukas Sichert
2026-07-15 8:15 ` [PATCH manager v3 1/2] ui: fabrics: make IPv4 interface column optional Lukas Sichert
2026-07-15 8:15 ` [PATCH manager v3 2/2] ui: fabrics: skip unsupported IP properties on submit Lukas Sichert
2026-07-15 12:24 ` Dominik Csapak [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=178411821561.2916317.4171483330747393973.b4-ty@b4 \
--to=d.csapak@proxmox.com \
--cc=l.sichert@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.