Deployment pipeline does not update default lakehouse in notebook

[Krumelur]

According to documentation, the deployment pipeline's auto binding feature should rebind my default lakehouse. But it does not.

Test scenario:

* In Dev Workspace creater a notebook and a lakehouse. Attach the lakehouse to the notebook.

* Deploy to Test using deployment pipelines.

* A binding between the Test and Dev assets will be created (both, for notebook and lakehouse)

* Navigate to the notebook in Test workspace and view its lineage. It will show that it's referencing the lakehouse from the Dev workspace, not the one in Test.

The only way to fix this is by creating a deployment rule for the notebook where I have to select the Dev lakehouse and manually enter the Test workspace ID and lakehouse ID.

This workaround becomes a nightmare to manage when you have a pipeline that references 20 notebooks because the deployment rule has to be configured 20 times individually and it must be remembered to always update it when adding a new notebook.

Question: Is this working as expected or a bug? I also observe that selecting a notebook in the deployment pipeline and using "Select related" will not select the lakehouse.

[Anonymous]

Hi @Krumelur 

We understand that the current practices for deploying notebooks through the deployment pipeline are not perfect. It still has many areas for improvement. I have found some ideas similar to your needs, and you can vote for them. The product team will understand your ideas and may include them in future plans.

Microsoft Idea: Data Pipelines - Create Relative Connection to Warehouse/Lakehouse/KQL DB

Microsoft Idea: The deployment pipeline should be configured to support multiple workspaces.

Microsoft Idea: add group configure rule in fabric deployment pipeline

Microsoft Idea: Only default lakehouse is visible on deployment rules for notebooks

Microsoft Idea: Fabric Deployment Pipelines - Deployment Rules

Best Regards,
Jing

Community Support Team

[Krumelur]

From what I learned, it's working "as designed", which makes me wonder what kind of design decision this was?

- As it is deploying lakehouses, it should reassign them automatically or at least let me choose to do so.

- If I am forced to use deployment rules, should it not make it as convenient as possible instead of updating dozens of lakehouses manually?

- If I must use the policies, why do I have to be the owner of the notebook to make the modification? I can change the notebook and even delete all of its content not being the owner, but I, as the admin, am unable to configure a deployment rule, really?

Curious to learn, what your take on it is.

[Joshrodgers123]

We're experiencing the same thing as well.

Deployment pipelines and git seem to be pretty unusable with Fabric and there doesn't seem to be much progress.

[AndyDDC]

I'm getting the same behaviour so I'll be investigating.