public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Ilya Krel <ikrel@blockbridge.com>
Subject: Re: [pve-devel] pve-manager/www: API for external plugins?
Date: Mon, 21 Nov 2022 09:26:21 +0100	[thread overview]
Message-ID: <Y3s2LbBQoTTNwVfn@rck.sh> (raw)
In-Reply-To: <c168209b-1a60-ca6a-d3e3-5d3476015d3a@proxmox.com>

Hi Thomas,

sorry for the long delay, and thanks for the pointers. In general we
would be willing to work on that if it does not take us too much effort.
We currently try to figure that out. A colleague of mine told me that
the js part should not be the problem, what I am not sure about is this
part:

On Fri, Nov 04, 2022 at 02:46:15PM +0100, Thomas Lamprecht wrote:
> If done somewhat nicely and safely we'd accept such a thing, the plugins
> would get an new method (e.g., api_schema) that returns a perl hash ref
> containing the properties including type, description and flags like if the
> setting is editable (after storage addition),

Okay, sure the plugins have to report their schema, I'm just not sure
about the "perl hash ref". How/where would/are the web part and the
plugins communicate? Would that be a real reference somewhere or would
the plugins just output a json dict that is somewhere parsed back?

> and a new API endpoint returning the schema's of all (external)
> plugins similar so that they can be shown in the add Drop down and
> used for creating the basic form.

Also obvious in general, I have the same problem of how and where do js
and perl code talk to each other.

Any hints and pointers in the right direction are welcome.

Best, rck



      reply	other threads:[~2022-11-21  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 10:28 Roland Kammerer
2022-11-04 13:46 ` Thomas Lamprecht
2022-11-21  8:26   ` Roland Kammerer [this message]

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=Y3s2LbBQoTTNwVfn@rck.sh \
    --to=roland.kammerer@linbit.com \
    --cc=ikrel@blockbridge.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal