Add clients to the API first, then have them checkin and get the right machineId

[sei-dupdyke]

Discussed in #336

^{Originally posted by danross826 May 3, 2024}
So, I have my ghosts api set up. Whenever I install a ghosts client on a new machine and link to my ghosts api server, it adds the machine to the database with a new machine id. However, I want to use the api to add machines before I install the client on them. Every machine has a machine id that's created an assigned to it when the client connects. How is this machine Id created? I've been looking through the code and I can see a function called at various points that creates a GUID. Is that function in the code somewhere (I can't find it if it is) or is it an inbuilt function of the language ghosts is using?

[sei-dupdyke]

I created a machine via the api:

{
  "id": "cfdb0a30-4c07-4963-818f-564d144dc956",
  "name": "test-001",
  "fqdn": "test-001.fqdn",
  "domain": "test-001.domain",
  "host": "test-001.host",
  "resolvedHost": "test-001.resolved.host",
  "hostIp": "2.2.2.2",
  "ipAddress": "3.3.3.3",
  "currentUsername": "user",
  "clientVersion": "8.0.0",
  "status": "Active",
}

which is really:

curl -X 'POST' \
  'http://0.0.0.0:5000/api/machines' \
  -H 'accept: */*' \
  -H 'Content-Type: application/json-patch+json' \
  -d '{
  "id": "cfdb0a30-4c07-4963-818f-564d144dc956",
  "name": "test-001",
  "fqdn": "test-001.fqdn",
  "domain": "test-001.domain",
  "host": "test-001.host",
  "resolvedHost": "test-001.resolved.host",
  "hostIp": "2.2.2.2",
  "ipAddress": "3.3.3.3",
  "currentUsername": "user",
  "clientVersion": "8.0.0",
  "status": "Active",
}'

and that returns

{
  "id": "cfdb0a30-4c07-4963-818f-564d144dc956",
  "name": "test-001",
  "fqdn": "test-001.fqdn",
  "domain": "test-001.domain",
  "host": "test-001.host",
  "resolvedHost": "test-001.resolved.host",
  "hostIp": "2.2.2.2",
  "ipAddress": "3.3.3.3",
  "currentUsername": "user",
  "clientVersion": "8.0.0",
  "history": [],
  "historyHealth": [],
  "historyTimeline": [],
  "historyTrackables": [],
  "status": "Active",
  "createdUtc": "2024-05-03T21:57:17.097161Z",
  "statusMessage": "Active & Up",
  "statusUp": "Up",
  "lastReportedUtc": "2024-05-03T21:57:17.117415Z",
  "hadId": false
}

So our ID is: "cfdb0a30-4c07-4963-818f-564d144dc956". I checked this in the database, and it indeed exists.

Then went to postman and created the headers that the ghosts client would pass:

ghosts-name:test-001
ghosts-fqdn:test-001.fqdn
ghosts-host:test-001.host
ghosts-domain:test-001.domain
ghosts-resolvedhost:test-001.resolved.host
ghosts-ip:2.2.2.2
ghosts-user:user
ghosts-version:8.0.0

and it works as expected.