pi-provider add: ask for what it needs instead of requiring every flag #81

New issue

Open

opened 2026-10-06 03:54:31 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-10-06 03:54:31 +01:00

Declaring the first provider on a fresh deployment is one long pi-provider add line: provider id, --credential, --url, one --target per VM and one --model per model, assembled from docs the operator has not read yet. discover-add removes the model list by reading the endpoint, but still takes the URL and targets as flags.

Proposal: pi-provider add (and discover-add) with no arguments asks for each thing it would otherwise take as a flag, in order: provider id, base URL, targets chosen from the inventory's libvirt dev VMs with all of them as the default, and the model list discovered from <base>/models with the option to type ids when discovery fails; then the existing hidden bearer prompt. Flags given on the command line skip their question, so scripts and the documented examples keep working unchanged. The dry run prints the same plan it prints today before anything is written.

Requested by the owner on the public install walk, declaring nullsink on a forge-less deployment.

Declaring the first provider on a fresh deployment is one long `pi-provider add` line: provider id, `--credential`, `--url`, one `--target` per VM and one `--model` per model, assembled from docs the operator has not read yet. `discover-add` removes the model list by reading the endpoint, but still takes the URL and targets as flags. Proposal: `pi-provider add` (and `discover-add`) with no arguments asks for each thing it would otherwise take as a flag, in order: provider id, base URL, targets chosen from the inventory's libvirt dev VMs with all of them as the default, and the model list discovered from `<base>/models` with the option to type ids when discovery fails; then the existing hidden bearer prompt. Flags given on the command line skip their question, so scripts and the documented examples keep working unchanged. The dry run prints the same plan it prints today before anything is written. Requested by the owner on the public install walk, declaring nullsink on a forge-less deployment.