From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id D256D1FF142 for ; Mon, 02 Mar 2026 14:45:10 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 561013433E; Mon, 2 Mar 2026 14:46:13 +0100 (CET) From: Lukas Sichert To: pdm-devel@lists.proxmox.com Subject: [PATCH manager 3/4] fix #7315: types: add missing storage flag to json schema Date: Mon, 2 Mar 2026 14:45:36 +0100 Message-ID: <20260302134537.108696-4-l.sichert@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260302134537.108696-1-l.sichert@proxmox.com> References: <20260302134537.108696-1-l.sichert@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.548 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: YCR6NGBHAADSGF5YA7VFTH7HLFZIKU3C X-Message-ID-Hash: YCR6NGBHAADSGF5YA7VFTH7HLFZIKU3C X-MailFrom: lsichert@pve.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Lukas Sichert X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: The response to the API-call '/cluster/resources' includes a shared flag for storages, that are also seen by other nodes in the cluster. But as this is not listed in the schema, the proxmox-datacenter backend cannot access the value. Add the missing `shared` boolean field to the schema definition of the API handler so the value is properly exposed. Signed-off-by: Lukas Sichert --- PVE/API2/Cluster.pm | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/PVE/API2/Cluster.pm b/PVE/API2/Cluster.pm index d6003a7d..062abaee 100644 --- a/PVE/API2/Cluster.pm +++ b/PVE/API2/Cluster.pm @@ -428,6 +428,11 @@ __PACKAGE__->register_method({ format => 'pve-storage-content-list', optional => 1, }, + shared => { + description => "Determines if the storage is shared", + type => 'boolean', + optional => 1, + }, plugintype => { description => "More specific type, if available.", type => 'string', -- 2.47.3