Open lukasjelonek opened 2 years ago
Suggestion:
Add aditional endpoints, e.g.
/admin/jobs
GET
-> List all jobs, Output the same as the current get jobs endpoint, but without the requirement to provide id-secret pairs. Pagination might be a good feature for this endpoint
/admin/jobs/{jobid}
or
GET
-> Get job details, including the configuration and the list of links to the files of this job
DELETE
-> Remove job
/admin/jobs/{jobid}/restart
POST
-> Restart the job
If a gRPC-style API is preferred over REST then the actions might be named:
/listAllJobs
-> No params
/getJobDetails
, /deleteJob
, /restartJob
-> The jobid as a string parameter would be sufficient
Add a secure endpoint for job management (list, restart, delete) or implement some other way to obtain and manipulate the jobs.
Required output: