Reintroduce Workspace Name visibility for Lakehouse References in Notebooks

[ram5]

In our setup, we work with multiple environments (Dev, Test, and Prod), each represented by its own workspace. To streamline deployment via pipelines, we keep Lakehouses and Notebooks named identical across workspaces.

Previously, when opening a Notebook, we could clearly see which Lakehouse it was connected to, including the workspace name it belonged to. 

This made it easy to identify if a Notebook was referencing, for example the Dev Lakehousem while working in the Prod workspace. We could then simply disconnect and re-add the correct reference.

However, with recent UI changes, only the Lakehouse name is visible, not the workspace it is contained in. This creates confusion when multiple Lakehouses share the same name across different workspaces. Even when adding a new source, the explorer does not clearly show which reference is from which workspace. This makes it far too easy to mistakenly remove or connect the wrong Lakehouse especially in production environments.

This seemingly small UI regression significantly affects productivity and introduces potential risks during deployment or debugging. Please consider restoring the visibility of workspace names to Lakehouse references in Notebooks.

Before: Screenshot from google

E.g:

Workspace Dev

-LakehouseA

-LakehouseB

....

Workspace Prod

-LakehouseA

-LakehouseB

....

After:

Only lakehouse name

We use same lakehouse name in each workspace

[giusepper11]

That is important for us here too!

[justin_berg1]

Agreed! This change was incredibly disruptive to our SDLC process

[lbilali]

this is being an issue for us as well maybe add a tooltip providing the name and the workspace where it is in a similar fashion as items in activity bar would be a solution