From: n.frey@proxmox.com
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager v2 0/4] api: add return schemas
Date: Wed, 24 Sep 2025 13:59:00 +0200 [thread overview]
Message-ID: <20250924115904.122696-1-n.frey@proxmox.com> (raw)
From: Nicolas Frey <n.frey@proxmox.com>
these four patches add the return schemas for endpoints in
ACMEPlugin, APT, ReplicationConfig and Services using the
createSchema() function where possible.
Also tested functionality using pvesh.
Changelog:
changes since v1, thanks to @ Thomas Lamprecht:
- use createSchema where possible (and sensible)
- redundant schema removed in APT.pm and Services.pm
- correct possible values and descriptions
Nicolas Frey (4):
api: add ACME plugin return schema
api: add APT versions return schema
api: add service state return schema
api: add replication config read return schema
PVE/API2/ACMEPlugin.pm | 15 ++---
PVE/API2/APT.pm | 113 ++++++++++++++++++++--------------
PVE/API2/ReplicationConfig.pm | 11 ++--
PVE/API2/Services.pm | 80 +++++++++++++++++++++++-
4 files changed, 156 insertions(+), 63 deletions(-)
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-24 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 11:59 n.frey [this message]
2025-09-24 11:59 ` [pve-devel] [PATCH pve-manager v2 1/4] api: add ACME plugin return schema n.frey
2025-09-24 11:59 ` [pve-devel] [PATCH pve-manager v2 2/4] api: add APT versions " n.frey
2025-10-02 8:50 ` Thomas Lamprecht
2025-10-02 9:25 ` Nicolas Frey
2025-09-24 11:59 ` [pve-devel] [PATCH pve-manager v2 3/4] api: add service state " n.frey
2025-09-24 11:59 ` [pve-devel] [PATCH pve-manager v2 4/4] api: add replication config read " n.frey
2025-10-02 8:51 ` Thomas Lamprecht
2025-10-02 11:18 ` Nicolas Frey
2025-10-02 8:23 ` [pve-devel] partially-applied: [PATCH pve-manager v2 0/4] api: add return schemas Thomas Lamprecht
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=20250924115904.122696-1-n.frey@proxmox.com \
--to=n.frey@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.