New-PveClusterSdnPrefixListsEntries
Create Prefix List Entry
API: POST /cluster/sdn/prefix-lists/{id}/entries, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveClusterSdnPrefixListsEntries [-PveTicket <PveTicket>] -Action <string> [-Ge <int>] -Id <string> [-Le <int>] [-LockToken <string>] -Prefix <string> [-Seq <long>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Action |
string |
Yes | Values: permit, deny. |
-Ge |
int |
No | |
-Id |
string |
Yes | The SDN prefix list identifier. |
-Le |
int |
No | |
-LockToken |
string |
No | the token for unlocking the global SDN configuration. |
-Prefix |
string |
Yes | |
-Seq |
long |
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
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
