Update Expected Machine
Update an existing Expected Machine by ID.
Org must have an Infrastructure Provider entity. User must have authorization role with PROVIDER_ADMIN suffix.
Infrastructure Provider must own the Expected Machine.
Alternatively, Tenant Admins with TargetedInstanceCreation capability can also update Expected Machines if they have an account with the Site’s Infrastructure Provider.
Authentication
export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current
Path parameters
Request
Expected Machine update request.
Provide defaultBmcUsername, defaultBmcPassword, or both to update BMC credentials. Each supplied value must be non-empty. Omitted credential fields and JSON null preserve the stored values. Credential removal is not supported.
ID of the Expected Machine to update.
For single updates, omit id or set it to null to use the ID from the URL path. A non-null body id must match the URL ID and use lowercase, hyphenated UUID format. Otherwise, REST returns HTTP 400.
Required and non-null in every batch update item.
Username for accessing the Expected Machine’s BMC. Omission or null preserves the value. A non-empty value can be supplied without defaultBmcPassword.
Password for accessing the Expected Machine’s BMC. Omission or null preserves the value. A non-empty value can be supplied without defaultBmcUsername.
Serial numbers of the Expected Machine’s fallback DPUs (Data Processing Units)
Complete expected host NIC list. Omission or null preserves the current list; an explicit empty list clears it.
Optional BMC IP address (IPv4 or IPv6). A non-empty address sets the value and pre-allocates a reserved IP for the BMC. It must not be unspecified, multicast, or IPv4 limited broadcast. An empty string clears the value. Omission or null preserves the current value.
When true, this host is eligible for DPF-based provisioning. Optional. Omission or null leaves the existing setting unchanged. An explicit true or false value updates the setting.
User-defined key-value pairs for organizing and categorizing Expected Machines
Optional per-host lifecycle profile
The Expected Machine’s BMC MAC address is immutable after creation. Omit this field, or provide another case/separator spelling of the current MAC as a compatibility no-op.
Response
MAC address of the Expected Machine’s BMC (Baseboard Management Controller)
Serial numbers of the Expected Machine’s fallback DPUs (Data Processing Units)
SKU information included when includeRelation=Sku is specified and the associated SKU belongs to this Expected Machine’s Site. For an association to another Site’s SKU, REST omits sku and returns the stored skuId.
Machine information included when includeRelation=Machine is specified and the associated Machine is found at this Expected Machine’s Site. For an association to another Site’s Machine, REST omits machine and returns the stored machineId.
Optional BMC IP address (IPv4 or IPv6). When set, pre-allocates a reserved IP for the BMC.
When true, this host is eligible for DPF-based provisioning. Returns the effective setting: true when no value is configured. An explicitly configured false value is returned as false.
User-defined key-value pairs for organizing and categorizing Expected Machines
Optional per-host lifecycle profile