The /metadata endpoint that outputs a complete metadata object is currently defined as the default for the --http-custom-endpoints flag instead of as a concrete endpoint in the HTTP handler implementation. Given its a part of the Equinix Metal metadata standard it should really be defined properly with an appropriate handler.
We're introducing a Hegel metadata API and dropping support for Equinix specific APIs which will see the removal of gRPC endpoints. We'll close this issue and await the Hegel API switch.
The
/metadata
endpoint that outputs a complete metadata object is currently defined as the default for the--http-custom-endpoints
flag instead of as a concrete endpoint in the HTTP handler implementation. Given its a part of the Equinix Metal metadata standard it should really be defined properly with an appropriate handler.