-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathswagger.yaml
80 lines (78 loc) · 1.92 KB
/
swagger.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
swagger: '2.0'
info:
title: API for Ingestion & Invoking Worker Flow
version: '0.1'
basePath: /api/v1/
consumes:
- application/json
produces:
- application/json
paths:
/liveness:
get:
tags:
- Service settings
operationId: f8a_admin.api_v1.get_liveness
summary: Get job service liveness
responses:
'200':
description: Service is alive
/readiness:
get:
tags:
- Service settings
operationId: f8a_admin.api_v1.get_readiness
summary: Get job service readiness
responses:
'200':
description: Service is ready
/worker-flow/{flow-name}:
post:
tags:
- Worker Flow
operationId: f8a_scanner.api_v1.worker_flow
summary: Invoke and start a worker flow
consumes:
- application/json
produces:
- application/json
parameters:
- in: "body"
name: "body"
description: "Data for the worker flow"
required: true
schema:
$ref: "#/definitions/WorkerJson"
- in: path
name: flow-name
description: name fo the worker flow that needs to be invoked
required: true
type: string
responses:
'202':
schema:
$ref: "#/definitions/WorkerResponse"
description: Worker Flow Invoked
'400':
description: Bad request from the client
'401':
description: Request unauthorized
'500':
description: Internal server error
definitions:
WorkerJson:
title: Data to invoke the worker flow
description: Data to invoke the worker flow
properties:
worker-data:
type: object
WorkerResponse:
title: Worker invocation call response
description: Response structure for worker invocation
properties:
status:
type: string
submitted_at:
type: string
id:
type: string