Git Branches - How to handle Notebook and Pipeline connections in different workspaces?

[tpenrose]

I have a DEV workspace: DEV1

Within this workspace are three items:

A lakehouse: LH1

A notebook: Notebook1

A pipeline: Pipeline1

The notebook points to LH1 as it's default lakehouse.

The pipeline has a single Lookup activity which points to LH1.

This workspace is connected to the Main branch of a git repo.

If I create a new branch ("feature1") and a new workspace ("DEV1-feature1"), Fabric will create the new branch and workspace and load all of the items listed above into the new "DEV1-feature1" workspace.

However, the notebook ("Notebook1") and the pipeline ("Pipeline1") in this new workspace will still reference the lakehouse ("LH1") from the orginial workspace ("DEV1").

I know how to repoint the notebook and the pipeline to the lakehouse within the new workspace.

However, if I do this and then merge my "feature1" branch back into the Main branch and then sync the original workspace ("DEV1") with the Main branch, then the DEV1 workspace's items will now be linking to the lakehouse in the "DEV1-feature1" workspace.

How can I ensure that notebooks and pipelines in a new branch reference a lakehouse within the "current" branch and not the original branch?

Without this ability, it appears that branching within Fabric is effectively useless. I'm really hoping I've missed something simple.

[tpenrose]

Thank you. I have now raised a Support ticket.

The Support ticket number is 2406280050002854.

[Anonymous]

Hi @tpenrose ,

Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

After creating a Support ticket please provide the ticket number as it would help us to track for more information.