From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager v3 2/2] api: add replication config read return schema
Date: Thu, 2 Oct 2025 14:47:28 +0200 [thread overview]
Message-ID: <20251002124728.103425-3-n.frey@proxmox.com> (raw)
In-Reply-To: <20251002124728.103425-1-n.frey@proxmox.com>
The return props now include programmatically added properties guest,
jobnum, and digest (the latter only being returned in read endpoint)
in addition to the create schema.
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
PVE/API2/ReplicationConfig.pm | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/PVE/API2/ReplicationConfig.pm b/PVE/API2/ReplicationConfig.pm
index 307ebe69..d62caa2a 100644
--- a/PVE/API2/ReplicationConfig.pm
+++ b/PVE/API2/ReplicationConfig.pm
@@ -17,6 +17,18 @@ use PVE::API2::Replication;
use base qw(PVE::RESTHandler);
+my $replication_api_return_props = {
+ PVE::ReplicationConfig->createSchema()->{properties}->%*,
+ guest => {
+ type => 'integer',
+ description => 'Guest ID.',
+ },
+ jobnum => {
+ type => 'integer',
+ description => 'Unique, sequential ID assigned to each job.',
+ },
+};
+
__PACKAGE__->register_method({
name => 'index',
path => '',
@@ -35,7 +47,7 @@ __PACKAGE__->register_method({
type => 'array',
items => {
type => "object",
- properties => {},
+ properties => $replication_api_return_props,
},
links => [{ rel => 'child', href => "{id}" }],
},
@@ -75,7 +87,13 @@ __PACKAGE__->register_method({
id => get_standard_option('pve-replication-id'),
},
},
- returns => { type => 'object' },
+ returns => {
+ type => "object",
+ properties => {
+ $replication_api_return_props->%*,
+ digest => get_standard_option('pve-config-digest'),
+ },
+ },
code => sub {
my ($param) = @_;
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-02 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 12:47 [pve-devel] [PATCH pve-manager v3 0/2] api: add return schemas Nicolas Frey
2025-10-02 12:47 ` [pve-devel] [PATCH pve-manager v3 1/2] api: add APT versions return schema Nicolas Frey
2025-10-02 12:47 ` Nicolas Frey [this message]
2025-10-03 12:58 ` [pve-devel] applied: [PATCH pve-manager v3 0/2] 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=20251002124728.103425-3-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.