unlhcc/HCCGo

Store cluster and other information in rootScope or Service

Closed this issue · 2 comments

Currently, the routed URL holds the cluster we are currently logged into. We should instead use some service or variable to store the currently logged in Cluster.

Was this already addressed somewhere? This information seems to already be stored in the connection service and fetched from that by the nav service.