Make route for the workspaces more user friendly

[benoitf]

Is your enhancement related to a problem? Please describe

Today I've routing to my workspaces that is using the following pattern:

https://che-eclipse-che.apps.my-cluster.com/workspace<tons-of-digits>/<endpoint-name>/<endpoint-port>

Describe the solution you'd like

I would rather have pattern

https://che-eclipse-che.apps.my-cluster.com/<username>/<workspace-name>/<endpoint-port> (endpoint-name being only required if there is several endpoints for a given port)

Describe alternatives you've considered

it could be anything that is more user friendly rather than tons of random digits

Additional context

No response

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[cgruver]

@l0rd I'd like to bump this request as well. I recently did a demo with an Angular app integrated with a Quarkus app on the backend via REST.

I had to hack the Angular app to inject the Route to the Quarkus app. https://github.com/eclipse-che-demo-app/che-demo-app/blob/main/setUiEnv.sh

WORKSPACE_ID=$(oc get devworkspace ${WORKSPACE_NAME} -o jsonpath={.status.devworkspaceId})
API_ROUTE=https://$(oc get route ${WORKSPACE_ID}-${CONTAINER_NAME}-${TARGET_PORT}-${ENDPOINT_NAME} -o jsonpath={.spec.host})
sed -i "s|${ENV_VAR}:.*|${ENV_VAR}: \'${API_ROUTE}\'|g" ${ENV_FILE_PATH}

It would be really nice if the route were predictable from information in the devfile.yaml.

[l0rd]

@cgruver assuming that it works (I am afraid that it doesn't today in Che) I would expose the quarkus application endpoint internally (exposure: internal) and configure the angular app to connect to the service. The service name is predictable (it's the endpoint name). Isn't that an option? I am asking to understand what we should prioritize.

[cgruver]

Unfortunately that would not work in this case. The angular app runs in the browser rather than server side. So a Route is the only way for it to talk to the backend API.

[dkwon17]

(endpoint-name being only required if there is several endpoints for a given port)

Hi @benoitf I'm not sure if I fully understand, what is the main use case of having several endpoints for a given port?

[benoitf]

I think probably I wanted to say 'workspace'. Like if I have multiple exposed ports to the outside