Update Machine
Update a Machine
Instance Type attribute updates, maintenance attribute updates and labels updates must be specified in separate requests. They cannot be processed at the same time.
Some attributes can only be updated by Provider, while others can be updated by Provider or a privileged Tenant.
For Infrastructure Providers: Org must have an Infrastructure Provider entity and own the Site that the Machine belongs to. User must have authorization role with PROVIDER_ADMIN suffix.
For Tenants: Org must have a Tenant with TargetedInstanceCreation capability enabled and Tenant Account with Machine’s Provider. User must have authorization role with TENANT_ADMIN suffix.
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
Set to true to enable maintenance mode and to false to disable maintenance mode. Can be set by Provider or privileged Tenant.
Describes the reason for moving Machine into maintenance mode. Required when setMaintenanceMode is true. Omit or set to null when setMaintenanceMode is omitted, null, or false; a non-null message is rejected in those cases. Can be updated by Provider or privileged Tenant.
Request to enter/exit online repair
Required when onlineRepair.enabled is true. Must not be set when exiting online repair (onlineRepair.enabled false).
Response
ID of the associated Instance, or null when unassigned. The association remains during termination until Instance inventory confirms deletion. A non-null value precludes Ready status.
Denotes architecture (x86 vs ARM) of the Machine
Only available to Providers. Returned if the includeMetadata query parameter is specified. Otherwise attribute is omitted from response.
User-specified Machine labels
Machine status combines the observed Core lifecycle with REST Instance assignment. A Ready Machine becomes InUse when REST assigns it, and remains InUse if Core reports Ready while the REST assignment still exists. Error, Maintenance, Initializing, and other non-Ready states retain precedence. When Instance deletion clears the assignment, InUse returns to Ready only if the retained Core snapshot reports Ready; otherwise fresh Machine inventory establishes the next status. Ready is not a reservation and does not guarantee that a subsequent Instance creation will succeed.
Date/time when the Machine was created
Date/time when the Machine was last updated