Retrieve a Machine
Org must have either an Infrastructure Provider entity or a Tenant entity.
If org has an Infrastructure Provider entity, then a user with PROVIDER_ADMIN role can request details for any Machine on any Site owned by the Provider.
If org has a Tenant entity, then a user with TENANT_ADMIN role can request details for any Machine associated with Tenant’s active Instances.
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
Query parameters
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