New-PveNodesStorageUpload
Upload templates, ISO images, OVAs and VM images.
API: POST /nodes/{node}/storage/{storage}/upload, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesStorageUpload [-PveTicket <PveTicket>] [-Checksum <string>] [-ChecksumAlgorithm <string>] -Content <string> -Filename <string> -Node <string> -Storage <string> [-Tmpfilename <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Checksum |
string |
No | The expected checksum of the file. |
-ChecksumAlgorithm |
string |
No | The algorithm to calculate the checksum of the file. Values: md5, sha1, sha224, sha256, sha384, sha512. |
-Content |
string |
Yes | Content type. Values: iso, vztmpl, import. |
-Filename |
string |
Yes | The name of the file to create. Caution: This will be normalized! |
-Node |
string |
Yes | The cluster node name. |
-Storage |
string |
Yes | The storage identifier. |
-Tmpfilename |
string |
No | The source file name. This parameter is usually set by the REST handler. You can only overwrite it when connecting to the trusted port on localhost. |
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.