Set-PveNodesConfig

Set node configuration options.

API: PUT /nodes/{node}/config, Proxmox VE API viewer

Syntax

Set-PveNodesConfig
    [-PveTicket <PveTicket>]
    [-Acme <string>]
    [-AcmedomainN <hashtable>]
    [-BallooningTarget <int>]
    [-Delete <string>]
    [-Description <string>]
    [-Digest <string>]
    [-Location <string>]
    -Node <string>
    [-StartallOnbootDelay <int>]
    [-Wakeonlan <string>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Acme	string	No	Node specific ACME settings.
-AcmedomainN	hashtable	No	ACME domain and validation plugin.
-BallooningTarget	int	No	RAM usage target for ballooning (in percent of total memory)
-Delete	string	No	A list of settings you want to delete.
-Description	string	No	Description for the Node. Shown in the web-interface node notes panel. This is saved as comment inside the configuration file.
-Digest	string	No	Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
-Location	string	No	The location of the node. Overrides the default from the datacenter config.
-Node	string	Yes	The cluster node name.
-StartallOnbootDelay	int	No	Initial delay in seconds, before starting all the Virtual Guests with on-boot enabled.
-Wakeonlan	string	No	Node specific wake on LAN settings.

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.