pulumi-vyos/Pulumi.yaml

name: vyos-proto
runtime: nodejs
description: Prototype — VyOS config subtrees as Pulumi resources, with commit-confirm
feat(pulumi-vyos): prototype VyOS subtrees as Pulumi resources with commit-confirm Goal: change VyOS and Kubernetes in one codebase and one plan -- so a BGP change touches both sides in a single `pulumi preview`. First, the worry about per-command pushes turned out to be unfounded for the community providers. Read foltik/vyos and its client library: a `vyos_config_block_tree` flattens the whole subtree into a single payload array and sends ONE POST to /configure, so one resource is one commit. Good. What they do not do is send `confirm_time`. Their payload is only op/path/value, so every change is an unprotected commit -- on a router you reach through the router, that is the difference between a mistake and an outage. The VyOS API itself supports commit-confirm; the providers simply do not use it. So this is a ~180-line Pulumi dynamic provider that does. Verified end to end on labsim: create and update each land in ~6s as one commit-confirmed transaction, update reports [diff: ~commands], destroy removes the subtree, and an unconfirmed commit was observed reverting the router on its own. Three API details found the hard way, all now encoded and commented: - confirm_time is ONLY read when the body parses as ConfigureListModel, i.e. {"commands": [...], "confirm_time": N}. A bare array is accepted and committed with NO timer armed, and the response looks like success. This silently discards the entire safety net, so the resource now checks the response actually says "commit-confirm" and refuses to proceed otherwise. - There is no /confirm endpoint; confirm is an op on /configure. - Confirm requires a `path` field even though it ignores it -- the Union resolves to ConfigureModel, which mandates path. Without it: "missing 'path' field", and the timer keeps running. Apply is `delete <path>` followed by the sets, in one request, so the result is the declared state rather than a merge -- otherwise `pulumi up` accumulates instead of converging. Known gaps, in the README rather than hidden: no read/refresh so out-of-band drift is not detected, and the API runs with a self-signed certificate and verification disabled. Both need addressing before production. The cutover itself should still use vyos-unifi-switch, which the API cannot replace. Sim left as found: test resource destroyed, dns forwarding restored to 15 lines. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DMVzWZgiKW2wquf5z8S1yH 2026-08-17 01:09:05 +01:00			`name: vyos-proto`
			`runtime: nodejs`
			`description: Prototype — VyOS config subtrees as Pulumi resources, with commit-confirm`