In the first iteration of the Toolforge jobs framework the API definition was done by hand.
There are now a number of indicators that having an OpenAPI definition (and generating the code from it) may be the right thing to introduce today.
See also:
- T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client
- T356377: [toolforge] simplify calling the different toolforge apis from within the containers
- https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Kubernetes/Jobs_framework#API_docs
- https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api