tests: add live VyOS e2e harness on Proxmox

Adds an opt-in end-to-end harness that runs pyvyos against a real
VyOS HTTPS API on a Proxmox VE host.

  tests/pve/      shell-based VM lifecycle on a remote PVE host:
                  preflight, ensure-template (state-machine over the
                  VMID with manual-install phase 1 and cloud-init
                  phase 2), create/start/stop/destroy, run-e2e.
                  Cloud-init seed ISO is generated on the PVE host
                  itself; nothing local-side beyond ssh is required.
                  .env is gitignored; .env.example documents the
                  full set of variables.

  tests/e2e/      pytest suite that exercises the public methods
                  most likely to regress on a payload change:
                  show, retrieve_show_config, configure_set /
                  retrieve_return_values / configure_delete round
                  trip, and configure_multiple_op batch. Auto-skipped
                  unless PYVYOS_E2E=1.

The cloud-init template now sets 'service https api rest' before
the API key. Without that flag VyOS only exposes /info; the other
HTTPS routes return 404. README and tests/pve/README document the
requirement, both for cloud-init and for the manual-fallback path.

Also fixes a pre-existing footgun in pyproject.toml: the pytest-env
defaults overwrote VYDEVICE_HOSTNAME from the shell, which made
the e2e tests silently aim at the stale 192.168.56.100 fixture
host. The entries now use the 'D:' (default) prefix so live runs
can override from the environment as expected.

Validated against VyOS rolling 2026.05.18-0045: 4 e2e + 57 unit
tests pass.

This commit does not change pyvyos HTTP payloads, request handling,
or response parsing.

1 files changed, 45 insertions, 0 deletions

diff --git a/tests/pve/preflight.sh b/tests/pve/preflight.sh
new file mode 100755
index 0000000..3fc6a16
--- /dev/null
+++ b/tests/pve/preflight.sh
@@ -0,0 +1,45 @@
+#!/usr/bin/env bash
+# tests/pve/preflight.sh — read-only sanity check on the PVE host.
+#
+# Verifies the host is reachable, has the tools the other scripts use,
+# and reports the current state of the template VMID and the e2e VMID
+# so you know whether ensure-template.sh / create-vm.sh have work to
+# do. Mutates nothing.
+
+set -euo pipefail
+
+HERE="$(cd "$(dirname "$0")" && pwd)"
+# shellcheck source=_lib.sh
+source "$HERE/_lib.sh"
+
+pve_load_env
+pve_require_reachable
+
+hdr "PVE identity"
+pve_ssh 'hostname; pveversion'
+
+hdr "Required tools (qm, pvesm, ip, curl, sha256sum)"
+pve_ssh 'for c in qm pvesm ip curl sha256sum; do
+  if command -v "$c" >/dev/null 2>&1; then
+    printf "  ok      %s\n" "$c"
+  else
+    printf "  MISSING %s\n" "$c"
+  fi
+done'
+
+hdr "Storage and bridge"
+pve_ssh "pvesm status; ip -br link show $PVE_BRIDGE 2>/dev/null || echo 'bridge $PVE_BRIDGE not found'"
+
+hdr "Image directory"
+pve_ssh "ls -la $PVE_IMAGE_DIR 2>/dev/null | head -20 || echo 'directory missing: $PVE_IMAGE_DIR'"
+
+hdr "Template VMID $VYOS_TEMPLATE_VMID"
+pve_ssh "qm status $VYOS_TEMPLATE_VMID 2>/dev/null \
+  && qm config $VYOS_TEMPLATE_VMID | grep -E '^(name|template|ostype|net0):' \
+  || echo 'template VMID $VYOS_TEMPLATE_VMID does not exist (ensure-template.sh will create it)'"
+
+hdr "e2e VMID $VYOS_E2E_VMID"
+pve_ssh "qm status $VYOS_E2E_VMID 2>/dev/null \
+  || echo 'e2e VMID $VYOS_E2E_VMID is free (create-vm.sh will clone it)'"
+
+hdr "ok"