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
Currently the "Open the service" button links to the first URL found in the urls field from the /my-lab/app endpoint.
These urls are derived from the paths of the service's Ingresses/Routes (see ServiceUrlResolver.getServiceUrls)
Feature request
In some cases, the most user-friendly entry point is a subpath of the default URL provided by the service's Ingress/Route (e.g. https://my-service.domain.fr/dashboard).
This user-friendly URL is often specified in the NOTES. Ideally, the "Open the service" button should use this URL instead of the raw urls field from the API.
Implementation considerations
Only URLs from the NOTES that match one of the service's Ingresses/Routes (as provided by the API) should be considered.
If multiple matching URLs exist in NOTES, the first encountered match should be used.
The text was updated successfully, but these errors were encountered:
Context
Currently the "Open the service" button links to the first URL found in the
urls
field from the/my-lab/app
endpoint.These
urls
are derived from the paths of the service'sIngresses
/Routes
(seeServiceUrlResolver.getServiceUrls
)Feature request
In some cases, the most user-friendly entry point is a subpath of the default URL provided by the service's
Ingress
/Route
(e.g. https://my-service.domain.fr/dashboard).This user-friendly URL is often specified in the NOTES. Ideally, the "Open the service" button should use this URL instead of the raw
urls
field from the API.Implementation considerations
Ingresses
/Routes
(as provided by the API) should be considered.The text was updated successfully, but these errors were encountered: