pve_sdn_ipam_update
Update an existing SDN IPAM integration in Proxmox VE. Dry-run returns a plan for review; confirm to stage the edit.
Instructions
MUTATION: update an SDN ipam integration (PENDING). type is IMMUTABLE.
token (if given) is redacted in the returned PLAN and never written to the audit
ledger. To create a new integration use pve_sdn_ipam_create; to remove one use
pve_sdn_ipam_delete. Dry-run by default (returns a PLAN, with the current config
CAPTURED and redacted); confirm=True stages the edit and returns {status, result}.
RISK_LOW (staging).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | New ipam API base URL. | |
| ipam | Yes | Existing SDN ipam integration id to update. | |
| token | No | New ipam API token — a SECRET, masked in plans/the ledger; forwarded raw on the wire. | |
| delete | No | Field names 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. | |
| section | No | New phpipam section id. | |
| lock_token | No | SDN cluster lock token to use for this write, if one is held. | |
| fingerprint | No | Certificate SHA-256 fingerprint (colon-separated hex byte pairs). | |
| 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
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |