SOS / OOB endpoint string in API /device response
complete
Daniel Lotterman
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.
Marques Johansson
complete
Daniel Lotterman
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",
M
Matt Mercer
In case it helps: the SOS endpoint seems to be
sos.<facility_code>.platformequinix.com
. Facility code is present as .facility.code
in the record returned by the GET /devices/{id}
API endpoint.