I'd like to share **pve-cli** (`pc`), an open-source command-line client for Proxmox VE — and Proxmox Datacenter Manager (PDM) — that I've been building and testing against live 9.x clusters.
The idea is "remote-first": you run `pc <resource> <action>` and the tool resolves which node hosts the guest for you (via `/cluster/resources`), so you rarely have to think about which node you're on. It speaks the official API with token *or* ticket auth, pins the server cert on first use (TOFU), and treats `json`/`yaml` output as a stable scripting contract (e.g. `pc vm show 100 -o json | jq .cores`).
Some usage examples can be found at https://github.com/ciroiriarte/pve-cli/blob/main/docs/cookbook.md
It's a single static Go binary (man pages + shell completions included), Apache-2.0 licensed.
Repo & releases: https://github.com/ciroiriarte/pve-cli
After some years using PVE on my own, I found the need to provide access to power users via CLI without allowing them SSH access to the PVE hosts. Feedback, bug reports, and feature ideas are very welcome — especially from anyone running larger or multi-cluster setups. Thanks!
The idea is "remote-first": you run `pc <resource> <action>` and the tool resolves which node hosts the guest for you (via `/cluster/resources`), so you rarely have to think about which node you're on. It speaks the official API with token *or* ticket auth, pins the server cert on first use (TOFU), and treats `json`/`yaml` output as a stable scripting contract (e.g. `pc vm show 100 -o json | jq .cores`).
Some usage examples can be found at https://github.com/ciroiriarte/pve-cli/blob/main/docs/cookbook.md
It's a single static Go binary (man pages + shell completions included), Apache-2.0 licensed.
Repo & releases: https://github.com/ciroiriarte/pve-cli
After some years using PVE on my own, I found the need to provide access to power users via CLI without allowing them SSH access to the PVE hosts. Feedback, bug reports, and feature ideas are very welcome — especially from anyone running larger or multi-cluster setups. Thanks!
Last edited:
). Since I know enough Go to be dangerous, I'd consider trying to start contributing - but before I do, would like to know if/that you have concrete plans to continue working on this project. Do you?