Not sure if this is the same thing, but following this https://cloud.google.com/compute/docs/instances/get-uuid#win… I get a different value to the `id` I got back from the POST instances API when I created it. Perhaps there's a different method? For now I can work around it by setting a UUID in the env via cloud-init which I can use in subsequent messaging, but it's a bit hand-held.
I just accidentally discovered the meta-data file on the CDROM volume on the instance I just fired up, which contains a meta-data file, including the instance ID I was looking for. Is this going to stay there? If so that will do nicely!
Yeah that's our cloud-init disk, I'm inclined to say yes this will stay there, theres no plans to move to another provisioning method
The metadata endpoint is a pretty good idea, adding it to our backlog.
huh this is surprisingly valid, though i believe the hostnode is the vmuuid