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 8E98E1FF187 for ; Mon, 8 Sep 2025 21:24:16 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D54CA19A4A; Mon, 8 Sep 2025 21:24:16 +0200 (CEST) Message-ID: <882e278b-e588-4099-b52f-4a32696cee8c@proxmox.com> Date: Mon, 8 Sep 2025 21:23:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox VE development discussion , "Max R. Carrara" References: <20250908180058.530119-1-m.carrara@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20250908180058.530119-1-m.carrara@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757359399768 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.029 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 Subject: Re: [pve-devel] [RFC pve-storage, pve-manager master v1 00/12] GUI Support for Custom Storage Plugins 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" Am 08.09.25 um 20:01 schrieb Max R. Carrara: > GUI Support for Custom Storage Plugins > ====================================== > > tl;dr: > > Add an API method to PVE::Storage::Plugin that returns the definition > for the form view of custom storage plugins. This definition is used by > the frontend to build the form view for creating / editing the storage > config entry of the plugin. The ultimate goal here is that custom > storage plugin devs don't have to (and also *must not*) ever touch > JavaScript to make their plugins show up in the GUI. Did not check the changes in full, but I see no mentioning of the ACME DNS plugins, which already provide such a mechanism, albeit a bit lower level with no real control how the fields get layouted. Did you check that out and maybe already re-used the underlying parts of the implementation but just not referenced it, or is this something completely new/custom? Further, FWICT this seems to add some parallel infra and need of definitions, might we get away with "just" annotating the existing schemas a bit better, i.e. add the flags for signaling secrets and potentially some layout hints, as the core importance is to be able to input required data to configure a storage, not that it needs to look "perfect", at least not in the initial version of this implementation, as adding more features and complexer layouting later on, especially once we got feedback from integrators and see how they use it. As it's much easier to see what's really required and what might be rather a (not much used) headache to maintain support for in ExtJS and a future Yew based UI. I.e., I'd be totally fine if the initial version would basically look like what the ACME DNS plugin UI does, focusing purely on required parameters, data types and validation over layout. Btw. this is partially related to [0] and I thought there was another issue tracking this, but couldn't find one from a quick search. [0]: https://bugzilla.proxmox.com/show_bug.cgi?id=3420 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel