action #56426

Yaml API routes shouldn't be experimental

Added by coolo 6 months ago. Updated 6 months ago.

Status:ResolvedStart date:03/09/2019
Priority:NormalDue date:
Assignee:cdywan% Done:


Category:Feature requests
Target version:Current Sprint


We should really open the gates for teams to post their yaml as they like.

I suggest we move the api route to a more official place, but require a format parameter so that we can 'force' teams to update
their usage if we need to change the format later on.


#1 Updated by cdywan 6 months ago

Semi-related: the $id used in the JSON schema JobTemplate.yaml currently still points to the non-existing We should fix this so people can validate whatever they're maintaining in repos elsewhere - we'll always validate the input of course.

The format could then be something like yaml-jobs-v1 comprised of the format, the name of the schema, and a version.

#2 Updated by cdywan 6 months ago

  • Status changed from New to In Progress
  • Assignee set to cdywan
  • Target version changed from Ready to Current Sprint

#4 Updated by cdywan 6 months ago

Follow-up for publication of the schema

#5 Updated by cdywan 6 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF