Skip to content

Commit

Permalink
fix some HTTP status codes
Browse files Browse the repository at this point in the history
  • Loading branch information
gbicann committed Sep 17, 2024
1 parent cde18a2 commit aa5b86d
Showing 1 changed file with 14 additions and 6 deletions.
20 changes: 14 additions & 6 deletions rst-api-spec.yaml.in
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,14 @@ info:

### Change Log

* 2024-09-17: The following endpoints responded with a `201` HTTP status,
when `204` should have been used:
* `GET /v1/heartbeat`
* `POST /v1/test/{id}/inputs`
* `POST /v1/test/{id}/files`
* `POST /v1/test/{id}/result`
* `PUT /v1/table/{id}`
* `DELETE /v1/table/{id}`
* 2024-09-12: Clarified access control rules for IDN table objects so users
can always access the objects they created.
* 2024-09-04:
Expand Down Expand Up @@ -229,7 +237,7 @@ paths:
operationId: heartbeat
responses:
#exec gpp -x inc/http-errors.yaml | sed 's/^/ /'
'201':
'204':
description: A successful result.

/v1/test:
Expand Down Expand Up @@ -325,7 +333,7 @@ paths:
$ref: "#/components/schemas/inputParameters"
responses:
#exec gpp -x inc/http-errors.yaml | sed 's/^/ /'
'201':
'204':
description: A successful result.

/v1/test/{id}/files:
Expand Down Expand Up @@ -364,7 +372,7 @@ paths:
format: binary
responses:
#exec gpp -x inc/http-errors.yaml | sed 's/^/ /'
'201':
'204':
description: A successful result.

/v1/test/{id}/file/{file}:
Expand Down Expand Up @@ -484,7 +492,7 @@ paths:
- cancelled
responses:
#exec gpp -x inc/http-errors.yaml | sed 's/^/ /'
'201':
'204':
description: A succesful result.

/v1/tests:
Expand Down Expand Up @@ -623,7 +631,7 @@ paths:
$ref: "#/components/schemas/idnTableRequest"
responses:
#exec gpp -x inc/http-errors.yaml | sed 's/^/ /'
'201':
'204':
description: A successful result.

delete:
Expand All @@ -641,7 +649,7 @@ paths:

INTERNAL_USER_ACCESS_CONTROL_POLICY
responses:
'201':
'204':
description: A successful result.

/v1/tables:
Expand Down

0 comments on commit aa5b86d

Please sign in to comment.