launch endpoint (no auth, no params, return: path) also test jupyter use case

added 1 deleted label

changed time estimate to 2d

added In Progress label and removed 1 deleted label

The launch endpoint should simply be called /launch, right?

Should we return a 301 response for redirect, this fits well with what @himanel1 wants for the UX, or a custom json response with the URL that the client can handle how they like? Or maybe have a parameter to allow the API user to decide?

/launch sounds good to me.

I would return a custom JSON response with status 200. In the JSON I would put a status message and the url once it is known. This way we use the HTTP codes kind of right: 200 means that the API handled the request correctly (although the container may not be ready yet), anything else brings up an error in the GUI.

The GUI will then handle the redirecting. 301 would mean permanent redirect which is maybe a bit different...? HTTP codes are such a mess

mentioned in commit 12388780

mentioned in merge request !5 (merged)

added 4h of time spent

mentioned in commit ff17bfd8

mentioned in commit 55543853

mentioned in commit c4416f36

created branch 14-launch-endpoint-no-auth-no-params-return-path-also-test-jupyter-use-case to address this issue

mentioned in merge request !8 (merged)

added Review label and removed In Progress label

added Test label and removed Review label

added DONE label and removed Test label

closed

removed DONE label