Set-PveClusterSdnRouteMapsEntriesEntry

Update Route Map Entry

API: PUT /cluster/sdn/route-maps/entries/{route-map-id}/entry/{order}, Proxmox VE API viewer

Syntax

Set-PveClusterSdnRouteMapsEntriesEntry
    [-PveTicket <PveTicket>]
    [-Action <string>]
    [-Call <string>]
    [-Delete <array>]
    [-Digest <string>]
    [-ExitAction <string>]
    [-LockToken <string>]
    [-Match <array>]
    -Order <int>
    -RouteMapId <string>
    [-Set <array>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Action	string	No	Matching policy of a route map entry. Values: permit, deny.
-Call	string	No	The SDN route map identifier.
-Delete	array	No
-Digest	string	No	Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications.
-ExitAction	string	No
-LockToken	string	No	the token for unlocking the global SDN configuration.
-Match	array	No
-Order	int	Yes	The index of this route map entry.
-RouteMapId	string	Yes	The SDN route map identifier.
-Set	array	No

Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.

Output

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.