Jobsets: update schema to align with the API
To further align with the API, we return custom JSON in order to display a `visible` field rather than `hidden` -- a `PUT` request expects `visible`, while a `GET` request returns `hidden`. This also allows us to rename the `jobsetinputs` field to `inputs` for the same reason: `PUT` expects `inputs`, while `GET` returns `jobsetinputs`.
This commit is contained in:
committed by
Graham Christensen
parent
d23f431889
commit
f1dd5d202e
@ -642,8 +642,8 @@ components:
|
||||
enableemail:
|
||||
description: when true the jobset sends emails when previously-successful builds fail
|
||||
type: boolean
|
||||
hidden:
|
||||
description: when false the jobset is visible in the web frontend
|
||||
visible:
|
||||
description: when true the jobset is visible in the web frontend
|
||||
type: boolean
|
||||
emailoverride:
|
||||
description: email address to send notices to instead of the package maintainer (can be a comma separated list)
|
||||
@ -667,12 +667,12 @@ components:
|
||||
type: integer
|
||||
type:
|
||||
description: the type of the jobset
|
||||
type: string
|
||||
type: integer
|
||||
flake:
|
||||
nullable: true
|
||||
description: the flake uri to evaluate
|
||||
type: string
|
||||
jobsetinputs:
|
||||
inputs:
|
||||
description: inputs configured for this jobset
|
||||
type: object
|
||||
additionalProperties:
|
||||
|
Reference in New Issue
Block a user