I left a couple of TODOs, which should be addressed in the future:
45
At the moment, the /api/alpha/deployments/{uuid}/logs endpoint returns ND-JSON, which needs to be manually parsed to turn it into valid JSON. I suggest to let the endpoint return a valid JSON array.
46
At the moment, it seems that the /api/alpha/deployments/{uuid}/logs endpoint returns all logs of the deployment. We should restrict it to the last X lines to prevent performance issues in both the server and the client. We should make X configurable both via a query parameter (e.g., /api/alpha/deployments/{uuid}/logs?limit=X) and via a configuration property in the application.yml.
47
It seems that the SSE-endpoint, /api/alpha/deployments/{uuid}/watch-logs, is slightly unstable. Before using that in the UI, we should further investigate it and make it more robust.
This PR implements the UI for deployments. Deployments are now a top-level item in our navigation.
In the UI, you can:
Try it out
You can explore and try out the changes as follows:
http://localhost:3000
in your browserTodos
I left a couple of TODOs, which should be addressed in the future:
45
At the moment, the
/api/alpha/deployments/{uuid}/logs
endpoint returns ND-JSON, which needs to be manually parsed to turn it into valid JSON. I suggest to let the endpoint return a valid JSON array.46
At the moment, it seems that the
/api/alpha/deployments/{uuid}/logs
endpoint returns all logs of the deployment. We should restrict it to the last X lines to prevent performance issues in both the server and the client. We should make X configurable both via a query parameter (e.g.,/api/alpha/deployments/{uuid}/logs?limit=X
) and via a configuration property in theapplication.yml
.47
It seems that the SSE-endpoint,
/api/alpha/deployments/{uuid}/watch-logs
, is slightly unstable. Before using that in the UI, we should further investigate it and make it more robust.