From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 19AAC1FF183 for ; Wed, 5 Nov 2025 09:21:42 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 376111DA32; Wed, 5 Nov 2025 09:22:20 +0100 (CET) Date: Wed, 05 Nov 2025 09:22:13 +0100 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox VE development discussion References: <20251006112409.2141871-1-d.csapak@proxmox.com> In-Reply-To: <20251006112409.2141871-1-d.csapak@proxmox.com> MIME-Version: 1.0 User-Agent: astroid/0.17.0 (https://github.com/astroidmail/astroid) Message-Id: <1762330923.48cwkorf6s.astroid@yuna.none> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762330918190 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.048 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [storage.pm, status.pm, proxmox.com] Subject: [pve-devel] applied-series: [PATCH manager/storage 0/3] Improve return schema for storage listing X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" thanks! On October 6, 2025 1:24 pm, Dominik Csapak wrote: > when calling the storage listing with `format=1`, we return additional information > about the storage about which formats are supported. > > The current return values/schema is bad and not describable by the JSONSchema, > so add a new property with a better schema. > > With this, our rust api schema generator will be able to handle this properly. > > This was noticed by dietmar when trying to use this api from rust. > > pve-storage: > > Dominik Csapak (2): > api: try to add more return schema information > api: list: return 'formats' info in a better structured way > > src/PVE/API2/Storage/Status.pm | 40 ++++++++++++++++++++++++++++++++++ > src/PVE/Storage.pm | 12 ++++++++++ > 2 files changed, 52 insertions(+) > > > pve-manager: > > Dominik Csapak (1): > ui: disk storage selector: use new api return format > > www/manager6/form/DiskStorageSelector.js | 20 ++++++++++++++++---- > 1 file changed, 16 insertions(+), 4 deletions(-) > > > Summary over all repositories: > 3 files changed, 68 insertions(+), 4 deletions(-) > > -- > Generated by git-murpp 0.8.1 > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel