Actions
action #56426
closedYaml API routes shouldn't be experimental
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2019-09-03
Due date:
% Done:
0%
Estimated time:
Description
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.
Updated by livdywan over 4 years ago
Semi-related: the $id used in the JSON schema JobTemplate.yaml currently still points to the non-existing open.qa/api/jobs/schema. 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.
Updated by livdywan over 4 years ago
- Status changed from New to In Progress
- Assignee set to livdywan
- Target version changed from Ready to Current Sprint
Updated by livdywan over 4 years ago
Updated by livdywan over 4 years ago
Follow-up for publication of the schema https://github.com/os-autoinst/openQA/pull/2322
Updated by livdywan over 4 years ago
- Status changed from In Progress to Resolved
Actions