From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: partially-applied: [PATCH proxmox, pve-{common,network,storage} v2 0/5] fix #7077: Improve error messages for ID verification
Date: Tue, 31 Mar 2026 22:39:34 +0200 [thread overview]
Message-ID: <177498957430.465431.15699262525583478154.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260206161236.335026-1-a.bied-charreton@proxmox.com>
On Fri, 06 Feb 2026 17:12:31 +0100, Arthur Bied-Charreton wrote:
> A lot of the logic around verifying ID constraints like their length,
> or that they follow a specific pattern, hides in registered format functions,
> which makes them invisible in the API docs.
>
> This series addresses this, as well as the not-ideal UX reported in #7077, by
> moving some of these checks to the registered JSON schemas and adding explicit
> length checks where no schema is defined.
>
> [...]
Applied the pve-network part for now, thanks!
[1/2] fix #7077: Enforce ID format in JSON schema definitions
commit: a8b6166768822e623c862b0bfd588ee022665241
[2/2] sdn: Remove unneeded registered formats
commit: ecf98c5d8f12fac9d61f3da27376aaab0ab598dc
prev parent reply other threads:[~2026-03-31 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 16:12 Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-common v2 1/1] fix #7077: Change JSON Schema attribute validation order Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-network v2 1/2] fix #7077: Enforce ID format in JSON schema definitions Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-network v2 2/2] sdn: Remove unneeded registered formats Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-storage v2 1/1] fix #7077: lvm: Improve ID verification error messages Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH proxmox v2 1/1] fix #7077: Improve SDN ID validation " Arthur Bied-Charreton
2026-03-31 20:39 ` Thomas Lamprecht [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=177498957430.465431.15699262525583478154.b4-ty@proxmox.com \
--to=t.lamprecht@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