Closed dsha256 closed 4 months ago
that's an illegal post action and is not documented in the docs. i am shocked though, it got allowed... It's not part of the routes, very strange.
I have just tried this and I cannot do that api action. <!DOCTYPE html>
Cannot POST /api/v1/job/451
ah, I see it's a put
it is meant for status changes, and is more an internal api. And I even wonder if it's used. I believe it is not and can be removed.
It does work on my end, but it's not meant to send extravars etc...
I have just tried this and I cannot do that api action.
Error Cannot POST /api/v1/job/451
I did that via the HTTP PUT. I saw that it is not documented in the Swagger docs but somehow it accepted the PUT request and according to the error, seems like a job ID is passed as a string to the query while it is an integer based on the migration SQL script to this repo.
it is meant for status changes, and is more an internal api. And I even wonder if it's used. I believe it is not and can be removed.
It does work on my end, but it's not meant to send extravars etc...
So by design, I'm not allowed to PUT or PATCH a job as an API user right?
correct. you launch a job and then abort/relaunch/delete, but you can't change it; Only internal code changes the job (status, timestamps, output, etc...)
I just double checked and the put is not used. I will remove it in the next version.
I'm trying to update an already louched job through the API endpoint
https://localhost:8443/api/v1/job/116
. I get 200 OK in PostmanBut, it's not updating actually. This is an error from the docker-compose logs: