case insensitive handling of UDF runtimes ?

[soxofaan]

Quite a bit of "ids" are accepted in case insensitive manner:

Format names MUST be accepted in a *case insensitive* manner throughout the API.

Billing plans MUST be handled in a *case insensitive* manner.

Service types MUST be accepted in a *case insensitive* manner.

Can we also do that for UDF runtimes?

Strictly speaking this is probably a breaking change, but I don't think that will break anything in practice.

[soxofaan]

side-note:

openeo-api/openapi.yaml

Line 2490 in c5a45b4

Service names MUST be accepted in a *case insensitive* manner throughout the API.

I think this should be Service types MUST be accepted... like done here:

openeo-api/openapi.yaml

Lines 5752 to 5753 in c5a45b4

	service types can be retrieved via `GET /service_types`. Service types
	MUST be accepted in a *case insensitive* manner.

[m-mohr]

That looks like an oversight, unfortunately.

[m-mohr]

On the other hand:

It is RECOMMENDED to use the following naming and casing:
* For programming langauge environments use the names as provided
in in the Scriptol List of Programming Languages.
* For docker images use the docker image identifier excluding the registry path.

[soxofaan]

hmm that note doesn't seem to be rendered on e.g. https://openeo.org/documentation/1.0/developers/api/reference.html

Also it recommends how runtimes should be named in the /udf_runtime response, not what backends must do when receiving a process graph with run_udf(..., runtime="pYthOn")

[m-mohr]

Yeah, ReDoc has some limitations and doesn't show everything.

Indeed, so right now it should be assumed to be case-sensitive.