@Seggan @emanresuA I have you on my list of people who've asked to use the ATO API, so I'm giving you advanced warning about backwards-incompatible changes to the API:
(If you're no longer using the API, or don't want to hear about these changes in future, please reply to this message, and I'll remove you from the list.)
The new API is not a huge change from the previous one, but the differences are:
- Output (stdout and stderr) are now streamed live from the program as it's running, so they are sent in separate WebSocket messages
- The stdout_truncated and stderr_truncated fields have been removed from the response (although they will probably be added back soon)
- Minor reformatting of the message schema to allow for multiple types of message
- Reflecting the backwards-incompatibility of these changes, the API URL has had a version bump to ato.pxeger.com/api/v1/ws/execute (previously v0)
I'm targeting roughly January 1st for these changes to be deployed; I know this is very much not the best time for API updates, but I'm prioritising the needs of end-users, who have wanted an update for quite a while. (The unfortunate truth is I don't care about the API users (you) as much. Sorry.)
I'd also like to mention that I'm hoping to reintroduce a simple pure-REST API (i.e. not using WebSockets) at some point soon™. If that interests you and you'd like to give any design input, let me know.
