pve_sdn_controller_create
Create a staged SDN controller with a specified type (bgp, evpn, faucet, isis) and protocol-specific options. Dry-run returns a plan; confirm executes the pending creation.
Instructions
MUTATION: create an SDN controller (PENDING — inert until pve_sdn_apply).
controller_type is bgp/evpn/faucet/isis; options carries the protocol-conditional
fields — generic passthrough, PVE validates per type. To update an existing controller
use pve_sdn_controller_update; to remove one use pve_sdn_controller_delete. Dry-run by
default (returns a PLAN); confirm=True creates the pending controller, returning
{status, result}. RISK_LOW (staging, no live network effect).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | False (default) returns a dry-run PLAN only; True executes the staged mutation. | |
| options | No | Type-specific fields (asn, peers, isis-domain, fabric, node, nodes, ...); PVE validates per type server-side. | |
| controller | Yes | New SDN controller id to create. | |
| lock_token | No | SDN cluster lock token to use for this write, if one is held. | |
| proximo_target | No | Which configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call. | |
| controller_type | Yes | Controller type: bgp, evpn, faucet, or isis. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |