From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH common v5 02/28] rest handler: handle: respect schema's 'type-property' when resolving type
Date: Mon, 19 Oct 2026 16:45:44 +0200 [thread overview]
Message-ID: <20261019144629.215541-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20261019144629.215541-1-f.ebner@proxmox.com>
For the HA resources 'migrate' endpoint, the plan is to use a oneOf
schema with the type parameter being 'resource-type' and a
resolve_type() function resolving the resource type based on the
service ID, which consists of the resource type and the numerical ID
of the resource. Resolve the type property instead of hard-coding
'type' and add a test case modeled after the above use case.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
No changes in v5.
src/PVE/JSONSchema.pm | 10 +++
src/PVE/RESTHandler.pm | 21 ++++--
test/get-options-test.pl | 150 +++++++++++++++++++++++++++++++++++++++
3 files changed, 174 insertions(+), 7 deletions(-)
diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm
index 34f2949..4b4842d 100644
--- a/src/PVE/JSONSchema.pm
+++ b/src/PVE/JSONSchema.pm
@@ -2254,6 +2254,16 @@ sub get_object_property_schema($schema, $key, $object_data = undef) {
return;
}
+# Get the type property of an object-like schema. Returns undef if there is no type property.
+sub get_object_type_property($schema) {
+ if (my $all_of = $schema->{allOf}) {
+ for my $subschema ($all_of->@*) {
+ return $subschema->{'type-property'} if defined($subschema->{'type-property'});
+ }
+ }
+ return $schema->{'type-property'};
+}
+
# $schema: an object-like schema
# $sub: sub($key, $schema, $one_of_instance_info) ->
# () empty list -> continue
diff --git a/src/PVE/RESTHandler.pm b/src/PVE/RESTHandler.pm
index dc6f329..316ce3a 100644
--- a/src/PVE/RESTHandler.pm
+++ b/src/PVE/RESTHandler.pm
@@ -522,14 +522,21 @@ sub handle {
# Type resolution must happen before normalization, since normalization needs to know
# the schema of values, for which the type must already be known, otherwise the oneOf
# variants will be ignored and normalization silently skips over parameters.
- # The property name is fixed, matching the 'type-property' SectionConfig generates.
my $resolve_type_hook = $info->{resolve_type};
- if ($resolve_type_hook && ref($param) eq 'HASH' && !defined($param->{type})) {
- # The callback only inspects the parameters, so hand it a clone.
- my $resolved_type = $resolve_type_hook->(clone($param));
- # NOTE: the resolved type is passed on to the method's code, which must tolerate it.
- if (defined($resolved_type)) {
- $param->{type} = $resolved_type;
+ if ($resolve_type_hook && ref($param) eq 'HASH') {
+ my $type_property;
+ if (PVE::JSONSchema::is_object_like_schema($schema)) {
+ $type_property = PVE::JSONSchema::get_object_type_property($schema);
+ }
+ # TODO enforce that 'type-property' is defined instead of using a default?
+ $type_property //= 'type';
+ if (!defined($param->{$type_property})) {
+ # The callback only inspects the parameters, so hand it a clone.
+ my $resolved_type = $resolve_type_hook->(clone($param));
+ # NOTE: the resolved type is passed on to the method's code, which must tolerate it.
+ if (defined($resolved_type)) {
+ $param->{$type_property} = $resolved_type;
+ }
}
}
diff --git a/test/get-options-test.pl b/test/get-options-test.pl
index 6eeee37..154cd11 100755
--- a/test/get-options-test.pl
+++ b/test/get-options-test.pl
@@ -753,6 +753,156 @@ package DirectOneOf {
}
}
+package OneOfWithCustomResolvedTypeProperty {
+ usebase;
+
+ sub desc($class) {
+ "oneOf as top-level with a custom 'type-property' that is resolved via 'resolve_type'";
+ }
+
+ sub schema($class) {
+ my $implicit_type_discriminator = {
+ type => 'string',
+ description => 'A property from which the type can be deduced.',
+ enum => ['deduce-type-one', 'deduce-type-two'],
+ };
+ return {
+ 'type-property' => 'custom-type',
+ 'type-property-schema' => {
+ type => 'string',
+ description => 'The type.',
+ enum => ['one', 'two'],
+ },
+ oneOf => [
+ {
+ 'instance-type' => 'one',
+ additionalProperties => 0,
+ properties => {
+ 'implicit-type-discriminator' => $implicit_type_discriminator,
+ 'prop-one' => {
+ optional => 1,
+ type => 'string',
+ description => 'a or b',
+ enum => ['a', 'b'],
+ },
+ },
+ },
+ {
+ 'instance-type' => 'two',
+ additionalProperties => 0,
+ properties => {
+ 'implicit-type-discriminator' => $implicit_type_discriminator,
+ 'prop-two' => {
+ type => 'number',
+ description => 'number',
+ minimum => 3,
+ maximum => 100,
+ },
+ },
+ },
+ ],
+ };
+ }
+
+ sub additional_method_info($class) {
+ return (
+ resolve_type => sub {
+ my ($param) = @_;
+ return 'one' if $param->{'implicit-type-discriminator'} eq 'deduce-type-one';
+ return 'two' if $param->{'implicit-type-discriminator'} eq 'deduce-type-two';
+ die "unable to resolve type\n";
+ },
+ );
+ }
+
+ sub long_usage_str($class, $prefix) {
+ "USAGE: $prefix --custom-type <string> [OPTIONS]\n"
+ . " --custom-type <one | two>\n"
+ . "\t The type.\n" . "\n"
+ . " Conditional options:\n" . "\n"
+ . " [custom-type=one]\n" . "\n"
+ . " --implicit-type-discriminator <deduce-type-one | deduce-type-two>\n"
+ . "\t A property from which the type can be deduced.\n" . "\n"
+ . " --prop-one <a | b>\n"
+ . "\t a or b\n" . "\n"
+ . " [custom-type=two]\n" . "\n"
+ . " --implicit-type-discriminator <deduce-type-one | deduce-type-two>\n"
+ . "\t A property from which the type can be deduced.\n" . "\n"
+ . " --prop-two <number> (3 - 100)\n"
+ . "\t number\n" . "\n";
+ }
+
+ sub invocations($class) {
+ return (
+ {
+ desc => "implicit-type-discriminator parameter works",
+ args => [qw(--implicit-type-discriminator deduce-type-one)],
+ expected => {
+ 'custom-type' => 'one',
+ 'implicit-type-discriminator' => 'deduce-type-one',
+ },
+ },
+ {
+ desc => "valid options parse",
+ args => [qw(--implicit-type-discriminator deduce-type-one --prop-one a)],
+ expected => {
+ 'custom-type' => 'one',
+ 'implicit-type-discriminator' => 'deduce-type-one',
+ 'prop-one' => 'a',
+ },
+ },
+ {
+ desc => "invalid options are rejected",
+ args => [qw(--implicit-type-discriminator deduce-type-one --prop-invalid a)],
+ error => "400 unable to parse option\n",
+ },
+ {
+ desc => "optional arg_param is optional",
+ args => [qw(--implicit-type-discriminator deduce-type-one)],
+ arg_param => [qw(prop-one)],
+ expected => {
+ 'custom-type' => 'one',
+ 'implicit-type-discriminator' => 'deduce-type-one',
+ },
+ },
+ {
+ desc => "optional arg_param is functional",
+ args => [qw(--implicit-type-discriminator deduce-type-one b)],
+ arg_param => [qw(prop-one)],
+ expected => {
+ 'custom-type' => 'one',
+ 'implicit-type-discriminator' => 'deduce-type-one',
+ 'prop-one' => 'b',
+ },
+ },
+ {
+ desc => "mandatory arg_param is mandatory",
+ args => [qw(--implicit-type-discriminator deduce-type-two)],
+ arg_param => [qw(prop-two)],
+ error => "400 not enough arguments\n",
+ },
+ {
+ desc => "mandatory arg_param is is functional",
+ args => [qw(--implicit-type-discriminator deduce-type-two 33)],
+ arg_param => [qw(prop-two)],
+ expected => {
+ 'custom-type' => 'two',
+ 'implicit-type-discriminator' => 'deduce-type-two',
+ 'prop-two' => 33,
+ },
+ },
+ {
+ desc => "explicit type takes precedence",
+ args => [qw(--implicit-type-discriminator deduce-type-two --custom-type one)],
+ expected => {
+ 'custom-type' => 'one',
+ 'implicit-type-discriminator' => 'deduce-type-two',
+ },
+ },
+ );
+ }
+}
+
package OneOfArrayVsScalar {
usebase;
--
2.47.3
next prev parent reply other threads:[~2026-10-19 14:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:45 [PATCH-SERIES many v5 00/28] migration: strict config check for intra-cluster migration Fiona Ebner
2026-10-19 14:45 ` [PATCH common v5 01/28] tools: move version_cmp() helper from qemu-server Fiona Ebner
2026-10-19 14:45 ` Fiona Ebner [this message]
2026-10-19 14:45 ` [PATCH cluster v5 03/28] cluster: move pvecfg node version helpers " Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 04/28] manager: add missing PVE::HA::Resources import Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 05/28] update crm commands: align logging with next state started/stopped Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 06/28] manager: factor out helper to check if requested resource motion is valid Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 07/28] next state stopped: align logging for motion command with next_state_started() Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 08/28] next state {stopped,started}: factor out helper to handle motion command Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 09/28] lrm: resource migration: support extra migration options Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 10/28] change service state: support hash as a parameter value Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 11/28] next state: handle motion command: support migration options Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 12/28] resources: add migrate_json_properties() method Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 13/28] queue resource motion: support migration options Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 14/28] crm command: support JSON-style migrate command Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 15/28] api: resources: migration: support additional migration options Fiona Ebner
2026-10-19 14:45 ` [PATCH ha-manager v5 16/28] test: add test for " Fiona Ebner
2026-10-19 14:45 ` [PATCH qemu-server v5 17/28] helpers: move version_cmp() helper to pve-common Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 18/28] helpers: move pvecfg node version helpers to pve-cluster Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 19/28] api: migrate: allow forwarding certain migration properties to HA Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 20/28] fix #7053: api: migrate: pass 'with-conntrack-state' flag to HA migration Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 21/28] qm: mtunnel: reply when a command is unknown Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 22/28] qm: mtunnel: add 'conf' command to do strict configuration parsing Fiona Ebner
2026-10-19 14:46 ` [PATCH qemu-server v5 23/28] migration: intra-cluster: check config can be parsed on target node Fiona Ebner
2026-10-19 14:46 ` [PATCH container v5 24/28] api: migrate: allow forwarding certain migration properties to HA Fiona Ebner
2026-10-19 14:46 ` [PATCH container v5 25/28] pct: introduce mtunnel command Fiona Ebner
2026-10-19 14:46 ` [PATCH container v5 26/28] d/control: bump versioned build dependency for libpve-common-perl to 9.0.12 Fiona Ebner
2026-10-19 14:46 ` [PATCH container v5 27/28] migration: intra-cluster: check config can be parsed on target node Fiona Ebner
2026-10-19 14:46 ` [PATCH manager v5 28/28] ui: migrate: add checkbox to allow skipping newly enforced config check Fiona Ebner
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=20261019144629.215541-3-f.ebner@proxmox.com \
--to=f.ebner@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.