Set-PveClusterSdnPrefixListsEntries
Update Prefix List Entry
API: PUT /cluster/sdn/prefix-lists/{id}/entries/{url_seq}, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterSdnPrefixListsEntries [-PveTicket <PveTicket>] [-Action <string>] [-Delete <array>] [-Digest <string>] [-Ge <int>] [-Le <int>] [-LockToken <string>] [-Prefix <string>] [-Seq <long>] -Id <string> -UrlSeq <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Action |
string |
No | Values: permit, deny. |
-Delete |
array |
No | |
-Digest |
string |
No | Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. |
-Ge |
int |
No | |
-Le |
int |
No | |
-LockToken |
string |
No | the token for unlocking the global SDN configuration. |
-Prefix |
string |
No | |
-Seq |
long |
No | |
-Id |
string |
Yes | The ‘{id}’ part of the path. |
-UrlSeq |
string |
Yes | The ‘{url_seq}’ part of the path. |
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
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.