Return $metadata resource as odata + openapi spec

[fisehara]

Returning odata and openapi specs in json format.
Specs are scoped to the request permissions.
Different users (roles) will receive different metadata endpoints
and resources.

Change-type: minor
See: https://jel.ly.fish/thread-93132f4a-1885-43c4-ac8d-1c190052e7d9
See: https://jel.ly.fish/thread-4245cd32-8b76-4c1a-a195-c8615c41b321
Signed-off-by: Harald Fischer harald@balena.io

[fisehara]

FYI @vipulgupta2048

[JSReds]

out of curiosity, what is the difference between lodash Dictionary and pinejs-client-core Dictionary ?

[fisehara]

@JSReds good catch. thx! This is a mistake. I only needed to export the PermissionLookup and not change the type.
Fixed to not use lodash dictionary.

[shaunco]

@fisehara - would love to see this merged. I just set out to build a golang API wrapper for Balena and ran into the lack of $metadata pretty quickly. Exposing the $metadata endpoint would allow OData client generators in a bunch of languages produce clients.

[Page-]

What is this about?

[fisehara]

Noise ;) Deleted.

[Page-]

I prefer a for-of in general:

Suggested change

	Object.keys(openAPIJson.paths).forEach((i) => {
	for (const i of Object.keys(openAPIJson.paths)) {

[Page-]

I prefer the pattern of:

Suggested change

	if (
	openAPIJson?.paths[i]?.get?.responses?.['200']?.content?.[
	'application/json'
	]?.schema?.properties?.value
	) {
	openAPIJson.paths[i].get.responses['200'].content[
	'application/json'
	].schema.properties['d'] =
	openAPIJson.paths[i].get.responses['200'].content[
	'application/json'
	].schema.properties.value;
	delete openAPIJson.paths[i].get.responses['200'].content[
	'application/json'
	].schema.properties.value;
	}
	const properties = openAPIJson?.paths[i]?.get?.responses?.['200']?.content?.[
	'application/json'
	]?.schema?.properties
	if (properties?.value) {
	properties['d'] = properties.value;
	delete properties.value;
	}