pve_sdn_ipam_create
Create a new SDN IPAM integration (netbox/phpipam/pve). Returns a dry-run plan by default; confirm=True executes the mutation.
Instructions
MUTATION: create an SDN ipam integration (PENDING — inert until pve_sdn_apply).
ipam_type is netbox/phpipam/pve; url/token/section/fingerprint are all OPTIONAL on
create and shared identically across all 3 types (no per-type field variation in this
schema). token is a SECRET — redacted to "[redacted]" in the returned PLAN and never
written to the audit ledger; the real create call still carries it raw. To update an
existing integration use pve_sdn_ipam_update; to remove one use pve_sdn_ipam_delete.
Dry-run by default (returns a PLAN); confirm=True creates the pending integration,
returning {status, result}. RISK_LOW (staging, no live network effect).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Ipam API base URL (netbox/phpipam). | |
| ipam | Yes | New SDN ipam integration id to create. | |
| token | No | Ipam API token — a SECRET, masked in plans/the ledger; forwarded raw on the wire so the create actually works. | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the staged mutation. | |
| section | No | Phpipam section id. | |
| ipam_type | Yes | Ipam type: netbox, phpipam, or pve. | |
| 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 |