[Feature Request] - Hide Workspaces not local to Manager for zone you are accessing

[frznfngrs]

Is your feature request related to a problem? Please describe. The use case problem as follows In the case of a multi-region deployment, and a proxy across regions not desireable, the user is presented with Workspaces not available to the region manager they are currently logged into.

Describe the solution you'd like With a web manager in each region, with an external load balancer or not, It would be nice if we had the option to enable on workspaces to only be published for the specific zone for which they are accessing the manager for. So an alternative to proxying a connection, just hide the workspace altogether if it is not available locally. Currently it will publish it to the user anyway.

For instance, if I have duplicate backend resources in different regions, each with their own agents, I can restrict workspaces to those agents. But the Workspace will still show up on the users available, even though they cannot access the resource in the other region. I can restrict a workspace to a deployment zone, and to an agent, but I cant restrict what web managers it publishes to.

Describe alternatives you've considered I know proxying is the current answer, so that backend resource is always available. But if I have duplicate but not coupled backend resources, independent to the region, I dont want to see the unusable one.