You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We wanted to fetch the list of (running) sessions for an authenticated user in order to read the session's instance URLs. After having looked at the docs and interfaces, we found out the it's possible to get a list of running sessions, but they do not expose the instance URL as part of the response. Without that information, we cannot show a list of running sessions on the landing page or implement re-connect logic to ephemeral sessions
Describe the solution you'd like
Include the instance's URL in the list of running sessions per user so that we can redirect the user to this URL in order to resume the running session.
Describe alternatives you've considered
We currently use persistent sessions with a predictable naming scheme to circumvent the issue.
Cluster provider
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Thanks for the issue :)
The session URL is currently part of the Session object's status. This is currently not returned. It makes sense to adapt this to also return the session URL and potentially other status fields.
Is your feature request related to a problem? Please describe.
We wanted to fetch the list of (running) sessions for an authenticated user in order to read the session's instance URLs. After having looked at the docs and interfaces, we found out the it's possible to get a list of running sessions, but they do not expose the instance URL as part of the response. Without that information, we cannot show a list of running sessions on the landing page or implement re-connect logic to ephemeral sessions
Describe the solution you'd like
Include the instance's URL in the list of running sessions per user so that we can redirect the user to this URL in order to resume the running session.
Describe alternatives you've considered
We currently use persistent sessions with a predictable naming scheme to circumvent the issue.
Cluster provider
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: