This idea was imported from Canny. Originally created by: Daniel Lotterman. The current owner is: Sal Carrasco.
Right now the only place to get the entirety of a devices OOB / SOS SSH endpoint is through the UI.
You could recompose it with just the devices UUID but that requires lots of human screen scaping.
Putting it in the device endpoint would let it be grabbed easily by metalcli and raw API and found through the devices JSON.
Purely QoL enhancement to reduce round trips through the UI.
This comment was imported from Canny. Originally created by: Daniel Lotterman with 0 likes.
I believe this is now complete / resolved: The endpoint is tagged under the `sos` key in the devices JSON. "sos": "UUID@sos.sv15.platformequinix.com", https://deploy.equinix.com/developers/api/metal/#tag/Devices/operation/createDevice
This comment was imported from Canny. Originally created by: Matt Mercer with 0 likes.
In case it helps: the SOS endpoint seems to be `sos..platformequinix.com`. Facility code is present as `.facility.code` in the record returned by the `GET /devices/{id}` [API endpoint](https://deploy.equinix.com/developers/api/metal/#tag/Devices/operation/findDeviceById).