From: Nicolas Frey <n.frey@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager v2 4/4] api: add replication config read return schema
Date: Thu, 2 Oct 2025 13:18:40 +0200 [thread overview]
Message-ID: <86210406-483d-4d4c-b626-6c08763e7217@proxmox.com> (raw)
In-Reply-To: <4e4240c5-c41f-4c40-97c7-4bc1f47e6735@proxmox.com>
On 10/2/25 10:51 AM, Thomas Lamprecht wrote:
> Am 24.09.25 um 13:59 schrieb n.frey@proxmox.com:
>> From: Nicolas Frey <n.frey@proxmox.com>
>>
>> removed delete from schema for return types, as it is only used
>> in update/PUT.
>>
>> Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
>> ---
>> PVE/API2/ReplicationConfig.pm | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/PVE/API2/ReplicationConfig.pm b/PVE/API2/ReplicationConfig.pm
>> index 307ebe69..d6451d85 100644
>> --- a/PVE/API2/ReplicationConfig.pm
>> +++ b/PVE/API2/ReplicationConfig.pm
>> @@ -17,6 +17,10 @@ use PVE::API2::Replication;
>>
>> use base qw(PVE::RESTHandler);
>>
>> +my $replication_config_return_type = PVE::ReplicationConfig->createSchema();
>> +# delete only used in update endpoint
>> +delete $replication_config_return_type->{delete};
>> +
>
> Which makes one rather wonder why it gets returned for the create schema in
> the first place – after all we do have a updateSchema
>
Thank you for pointing that out. That was an error on my part, I mixed up
code from createSchema/updateSchema. So removing 'delete' is redundant.
AFAICT the create schema *can* be used as the return for this endpoint,
as long as 'guest' and 'digest' properties are added (which I missed in
v2, I apologize).
>> __PACKAGE__->register_method({
>> name => 'index',
>> path => '',
>> @@ -33,10 +37,7 @@ __PACKAGE__->register_method({
>> },
>> returns => {
>> type => 'array',
>> - items => {
>> - type => "object",
>> - properties => {},
>> - },
>> + items => $replication_config_return_type,
>> links => [{ rel => 'child', href => "{id}" }],
>> },
>> code => sub {
>> @@ -75,7 +76,7 @@ __PACKAGE__->register_method({
>> id => get_standard_option('pve-replication-id'),
>> },
>> },
>> - returns => { type => 'object' },
>> + returns => $replication_config_return_type,
>> code => sub {
>> my ($param) = @_;
>>
>
_______________________________________________
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 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 11:59 [pve-devel] [PATCH pve-manager v2 0/4] api: add return schemas n.frey
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 [this message]
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=86210406-483d-4d4c-b626-6c08763e7217@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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