Get-PveNodesCephCfgValue
Get configured values from either ceph.conf or the mon config DB. Underscores in section and key names are normalised to hyphens in the response, regardless of how they’re written in the source.
API: GET /nodes/{node}/ceph/cfg/value, Proxmox VE API viewer
Syntax
Section titled “Syntax”Get-PveNodesCephCfgValue [-PveTicket <PveTicket>] -ConfigKeys <string> -Node <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-ConfigKeys |
string |
Yes | List of <section>:<config key> items separated by semicolon, comma or space. |
-Node |
string |
Yes | The cluster node name. |
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.
