Document lack of $metadata API endpoint

[brownjohnf]

We advertise an OData API, but we don't expose the $metadata endpoint. This should be documented clearly. Really, we should document all ways in which our exposed API differs from the OData standard/expected behavior.

Front conversations

[shaunco]

Is there a particular reason the /$metadata endpoint is not exposed? I just set out to build a go API wrapper for Balena and ran into this wall pretty quickly. Exposing the $metadata endpoint would allow OData client generators in a bunch of languages produce clients.

[shaunco]

@myarmolinsky ... was $metadata support added or the lack of it documented? I don't see either, but might just be overlooking it.

[myarmolinsky]

Hey @shaunco , I don't have any updates on $metadata. I intended to close this issue and many others as stale given that there has not been any activity on them in some time. If this is still something you are interesting in seeing addressed, I will reopen the issue.

[shaunco]

Thanks @myarmolinsky , was just confused because it was marked as "completed" rather than just being closed/stale

[myarmolinsky]

Yeah that was my mistake, a lot of the issues I closed were closed as completed instead of stale. But as long as folks vocalize that something is still an issue for them, I will happily reopen it.