Set-PveClusterNotificationsEndpointsGotify
Update existing gotify endpoint
API: PUT /cluster/notifications/endpoints/gotify/{name}, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterNotificationsEndpointsGotify [-PveTicket <PveTicket>] [-Comment <string>] [-Delete <array>] [-Digest <string>] [-Disable <bool>] -Name <string> [-Server <string>] [-Token <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Comment |
string |
No | Comment. |
-Delete |
array |
No | A list of settings you want to delete. |
-Digest |
string |
No | Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. |
-Disable |
bool |
No | Disable this target. |
-Name |
string |
Yes | The name of the endpoint. |
-Server |
string |
No | Server URL. |
-Token |
string |
No | Secret token. |
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.