pve_sdn_controller_update
Update an existing SDN controller's settings. Dry-run to view a plan, then confirm to apply changes.
Instructions
MUTATION: update an SDN controller (PENDING). type is IMMUTABLE — delete and
re-create to change it. options sets fields; delete unsets keys.
To create a new controller use pve_sdn_controller_create; to remove one use pve_sdn_controller_delete. Dry-run by default (returns a PLAN); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging; inert until pve_sdn_apply).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| delete | No | Controller option keys to unset. | |
| digest | No | Expected config digest for optimistic-concurrency checking. | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the staged mutation. | |
| options | No | Controller fields to set (type-specific — asn, peers, isis-domain, ...). | |
| controller | Yes | Existing SDN controller id to update. | |
| 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. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |