feat(dev): mTLS enrollment dev loop; retire dev-insecure plain-WS #78
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/VA-74-dev-mtls-enroll-bootstrap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Restore a one-command local dev loop in which a freshly built agent enrolls against the local vervain-server over mTLS and comes online, replacing the dev-insecure plain-WS path that VA-67 made inert.
just dev-enroll-bundle(and a privatemint-bundle) that logs in to the dev server with the bootstrapped site-admin and mints a single-use enrollment bundle (POST /api/v1/enroll-tokens) into run/: the four PEMs the agent's VERVAIN_*_FILE env vars point at plus a bootstrap.json in the shapeinstall --fromconsumes.just dev/dev-detach/dev-hostto bootstrap over mTLS: export VERVAIN_SERVER_DOMAIN + VERVAIN_*_FILE + VERVAIN_DB_KEY pointing at the bundle, auto-mint on first run, and reuse the identity stored in vervain-agent.db afterward. The container path reaches the server's in-network mTLS listener on :15443 with no host port-publish.dev-insecureCargo feature and its uses in compose.yml / justfile; drop the dead run/vervain-agent.vagent seed + template and the ws:// rendering (ensure-settings / ensure-settings-host).dev-insecureor a plain ws:// dev transport reappears in Cargo.toml, justfile, or compose.yml.#VA-74
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com