From: "Jakob Klocker" <j.klocker@proxmox.com>
To: "Max R. Carrara" <m.carrara@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins
Date: Mon, 03 Aug 2026 13:50:27 +0200 [thread overview]
Message-ID: <DKFABGUHM6IU.3FDYMNEV2ZA3U@proxmox.com> (raw)
In-Reply-To: <20260727143445.513900-1-m.carrara@proxmox.com>
I ran the same tests as in the previous version:
- adding sshfs plugin over the GUI
- editing a plugin over the GUI
- removing a plugin over the GUI
- checking the output of the new endpoints
everything worked as expected.
With the changes from the previous versions the code looks good to me.
Note that I don't have that much experience with the frontend, but
from what I can tell everything looks good.
A small side note: there isn't a unified Makefile style across the
codebase, which would make sense to have.
With that said, thanks for the patches and consider this:
Reviewed-by: Jakob Klocker <j.klocker@proxmox.com>
Tested-by: Jakob Klocker <j.klocker@proxmox.com>
On Mon Jul 27, 2026 at 4:34 PM CEST, Max R. Carrara wrote:
> GUI Support for Custom Storage Plugins - v3
> ===========================================
>
> Notable Changes Since v2
> ------------------------
>
> - Drop the patternProperties RFC patches.
>
> After some additional consideration, I decided that supporting
> patternProperties is out of scope for this series, and probably
> something that deserves its own series instead.
>
> In turn, the 'x-advanced' and 'x-hidden' keys in the plugin property
> schema returned by the new API endpoint are now set through two
> new hashes in `plugindata()`. This means that each plugin has to
> define which properties it considers advanced and which should be
> hidden in the UI itself, just like with sensitive properties.
>
> - Rename the 'sensitive' key that is returned as part of the plugin
> property schema by the new API endpoint to 'x-sensitive'. This is done
> in order to make it clear that this keyword is not part of our overall
> JSON schema, since each plugins' properties' schemas are returned
> directly.
>
> Note that we can still "promote" 'x-sensitive' and have it exist in
> the general JSON schema as 'sensitive' at some point in the future,
> but that's out of scope for this series.
>
> - Sort modules in patch #13 (thanks @Jakob for the suggestion!)
>
> - Update the SSHFS example plugin and make use of the new hashes in
> `plugindata()`, `title` keys in `properties()`, and also bump it's API
> version, with all changes that are necessary for this.
>
> Thanks again to everyone who reviewed and/or tested the previous
> iterations of this series, as well as to those that provided feedback!
> It's much appreciated.
>
> Previous Versions
> -----------------
>
> rfc-v1: https://lore.proxmox.com/pve-devel/20250908180058.530119-1-m.carrara@proxmox.com/
> rfc-v2: https://lore.proxmox.com/pve-devel/20251121165858.818307-1-m.carrara@proxmox.com/
> v1: https://lore.proxmox.com/pve-devel/20260623143402.772452-1-m.carrara@proxmox.com/
> v2: https://lore.proxmox.com/pve-devel/20260717154943.696411-1-m.carrara@proxmox.com/
> [SNIP]
next prev parent reply other threads:[~2026-08-03 11:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 14:34 [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-common v3 01/17] json schema: add multiline string format Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 02/17] api: plugins/storage: add initial routes and endpoints Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 03/17] api: plugins/storage/plugin: include schema in plugin metadata Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 04/17] api: plugins/storage/plugin: mark sensitive properties in schema Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 05/17] api: plugins/storage/plugin: factor plugin metadata code into helper Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 06/17] api: plugins/storage/plugin: add plugins' 'content' to their metadata Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 07/17] all plugins: add 'title' to properties, adapt 'description's Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 08/17] all plugins, api: mark certain properties as advanced in plugindata() Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 09/17] all plugins, api: mark certain properties as hidden " Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 10/17] form: introduce new 'proxmoxtextarea' field Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 11/17] utils: introduce helper function getFieldDefFromPropertySchema Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 12/17] acme: use helper to construct ExtJS fields from property schemas Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 13/17] api2: sort modules and API method registrations Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 14/17] api: add API routes 'plugins' and 'plugins/storage' Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 15/17] ui: storage view: display error when no editor for storage type exists Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 16/17] ui: storage: add basic UI integration for custom storage plugins Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage-plugin-examples v3 17/17] sshfs: Update SSHFS plugin Max R. Carrara
2026-08-03 11:50 ` Jakob Klocker [this message]
2026-08-03 13:27 ` [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins Jakob Klocker
2026-08-04 10:40 ` Thomas Ellmenreich
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=DKFABGUHM6IU.3FDYMNEV2ZA3U@proxmox.com \
--to=j.klocker@proxmox.com \
--cc=m.carrara@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox