Re: [pve-devel] storage plugins: what is plugindata()->{content}[1]

[Roland Kammerer via pve-devel <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 6735 bytes --]

From: Roland Kammerer <roland.kammerer@linbit.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] storage plugins: what is plugindata()->{content}[1]
Date: Fri, 7 Feb 2025 13:34:04 +0100
Message-ID: <Z6X9vOv2lCsvTy3o@arm64>

On Fri, Feb 07, 2025 at 10:18:42AM +0100, Fabian Grünbichler wrote:
> 
> > Roland Kammerer via pve-devel <pve-devel@lists.proxmox.com> hat am 07.02.2025 10:02 CET geschrieben:
> > Hi all,
> > 
> > rather simple question I guess, but I could not find the answer in
> > https://pve.proxmox.com/wiki/Storage_Plugin_Development and linked
> > documents and looks like my grep foo is lacking today, so here we go:
> > I guess I know what the first hash in the 'content' array is, but what
> > is the second? Actually, why is there a second one?
> > 
> > Storage/LVMPlugin.pm:
> > content => [ {images => 1, rootdir => 1}, { images => 1 }]
> > 
> > vs.
> > 
> > Storage/LvmThinPlugin.pm:
> > content => [ {images => 1, rootdir => 1}, { images => 1, rootdir => 1}]
> > 
> > Best, rck
> 
> the first one defines the allowed/valid content types, the second the default one(s):

thanks Fabian and Fiona, that explains it.

> we are working on improving the docs and cleaning all of this up!

that is great news, even after maintaining a plugin for some time it
usually takes a deep dive into some core code to actually understand
some of the API. If there is then something to review or give feedback
from an external plugin dev's point of view feel free to explicitly ping
me.

Best, rck


[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel