pve_sdn_route_map_entry_create
Create a route-map entry for Proxmox SDN routing policy. Match conditions and set actions define traffic treatment; dry-run plans changes before application.
Instructions
MUTATION: create a route-map entry (PENDING — inert until pve_sdn_apply). There is NO container-level 'create a route map' tool — a route map is defined purely by having >=1 entry.
To update an existing entry use pve_sdn_route_map_entry_update; to remove one use pve_sdn_route_map_entry_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending entry, returning {status, result}. RISK_LOW (staging, no live network effect).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| call | No | Another route-map id to invoke as a sub-routine. | |
| match | No | Array of {key, value} match-clause objects (route-type, vni, ip-address-prefix-list, metric, local-preference, peer, tag, ...); PVE validates each item's key server-side. | |
| order | Yes | Entry position (0-65535, required). | |
| action | Yes | Matching policy: 'permit' or 'deny'. | |
| digest | No | Expected config digest for optimistic-concurrency checking — accepted on CREATE for this endpoint (unlike prefix-list's own entry create, which has none). | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the staged mutation. | |
| lock_token | No | SDN cluster lock token to use for this write, if one is held. | |
| exit_action | No | Single {key, value} object: key is one of on-match-goto/on-match-next/continue. | |
| set_clauses | No | Array of {key, value} set-clause objects (ip-next-hop, local-preference, weight, metric, ...) — wire key is 'set'; renamed here to avoid shadowing the 'set' builtin. | |
| route_map_id | Yes | Route map id to add this entry to — a FREE-FORM id chosen by the caller; there is no separate 'create a route map' call, so the FIRST entry_create for a given id implicitly brings that route map into existence. | |
| 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 |