Is your feature request related to a problem? Please describe.
Deploying UI on the cloud makes it very difficult to make routing work because UI and respective services are running on the same URL address.
Describe the feature you are requesting, as well as the possible use case(s) for it.
We should have an optional prefix for the UI endpoints so we can easily route them based on it. The challenge is that we need to be aware of the prefix on the UI (i.e. we can't do it transparently from the code and only on the LB/reverse proxy level) due to the redirects we use to navigate UI.
Indicate the importance of this feature to you.
[ ] Must-have
[X] Should-have
[ ] Nice-to-have
Anything else?
It's worth exploring our options before taking the most intrusive way to implement it which will include changes in all the API layer code, and almost all the templates as well.
Is there an existing feature request for this?
Is your feature request related to a problem? Please describe.
Deploying UI on the cloud makes it very difficult to make routing work because UI and respective services are running on the same URL address.
Describe the feature you are requesting, as well as the possible use case(s) for it.
We should have an optional prefix for the UI endpoints so we can easily route them based on it. The challenge is that we need to be aware of the prefix on the UI (i.e. we can't do it transparently from the code and only on the LB/reverse proxy level) due to the redirects we use to navigate UI.
Indicate the importance of this feature to you.
Anything else?
It's worth exploring our options before taking the most intrusive way to implement it which will include changes in all the API layer code, and almost all the templates as well.