From: Wayne Seguin <wayneeseguin@fivetwenty.io>
To: Cyrus <cyruspy@gmail.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: CLI
Date: Tue, 21 Jul 2026 09:19:56 -0400 [thread overview]
Message-ID: <CAA7b_eRbxvr+GKjBZBP8nQ6YWh8bjc=NepwV_4523ncMjgwhbw@mail.gmail.com> (raw)
In-Reply-To: <CAEaLa5G_5sEW_uYcdqNexgUb4ZLNrnJ3zLfJrkAaZHXT_wjyXA@mail.gmail.com>
Hello Cyrus! I just saw your reply.
I also wrote one that we've been using; my approach is a bit different.
Please feel free to check it out, I would also love to receive feedback!
https://github.com/fivetwenty-io/proxmox-cli
Initial blog post and intro doc provide more context on the idea:
https://fivetwenty.io/insights/introducing-proxmox-cli-pmx-pve-pbs-pdm/
https://fivetwenty.io/proxmox/cli/
Essentially I am targeting support for the PVE, PBS, and PDM APIs. I also
need the ability to quickly spin up labs (single or cluster), which is why
there is also the `lab` subcommand that we have been using.
I hope that some folks find it useful!
Warm Regards,
~Wayne
On Thu, Jun 18, 2026 at 7:30 AM Cyrus <cyruspy@gmail.com> wrote:
> Hello,
>
> First furious sprint:
>
> https://github.com/ciroiriarte/pve-cli
>
> Would love to receive feedback.
>
> Regards,
>
> El mié, 27 may 2026 a las 17:02, Wayne Seguin
> (<wayneeseguin@fivetwenty.io>) escribió:
> >
> > I'm interested in potentially collaborating on such an effort if it
> isn't already around.
> >
> > On Tue, May 26, 2026 at 6:15 AM Cyrus <cyruspy@gmail.com> wrote:
> >>
> >> Hello!,
> >>
> >> I would like to have something like the Openstack CLI but for PVE, I'm
> >> pondering implementing it via:
> >>
> >> 1. Direct API interaction
> >> 2. An existing wrapper
> >>
> >> (2) should be easier, but I see too many implementations, and not clear
> winner:
> >> https://github.com/jefersonflus/Proxmox-PHP-SDK
> >> https://github.com/proxmoxer/proxmoxer
> >> https://pve.proxmox.com/wiki/Proxmox_VE_API#API_Client_Libraries
> >>
> >> Perl would not be my preferred language, but if API coverage is 100%,
> >> official libpve-apiclient-perl might be the way to go.
> >>
> >> How would you do it?.
> >>
> >> Regards,
> >> Cyrus.
> >>
> >>
>
prev parent reply other threads:[~2026-07-21 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 0:45 CLI Cyrus
[not found] ` <CAA7b_eTBT9tfBfR=6ZMDx9cYM9K6u+bapLyTShNeR9hHkeCnQQ@mail.gmail.com>
2026-06-18 11:30 ` CLI Cyrus
2026-07-21 13:19 ` Wayne Seguin [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='CAA7b_eRbxvr+GKjBZBP8nQ6YWh8bjc=NepwV_4523ncMjgwhbw@mail.gmail.com' \
--to=wayneeseguin@fivetwenty.io \
--cc=cyruspy@gmail.com \
--cc=pve-user@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.