Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

0

Change the way the notebook lakehouses is stored in source control

Hi,

Today, the lakehouses linked to the notebook and the default lakehouse are stored in comments in a .py file, with all the notebook code.

 

This makes the source control very difficult. If we would like to promote the notebook from development to test and to production and during this promotion we need to change the linked workspaces, it becomes very manual, or in need of devOps processing outside power bi.


If this configuration were located in a configuration file together the notebook (and there are already some json files created for each notebook), we could use gitignore to avoid the json configuration file to be published to the source control. In this way, the notebook could be promoted between environments and it would be linked to different lakehouses on each environment.

 

Kind Regards,

 

Dennes

 

Status: Delivered

Hi @DennesTorres 

 

It doesn't seem to be able to convert notebook format to .json format. However, you can try to create three project branches for it, Dev,Prod,Master.It also manages the code and provides environment testing as well.

 

Best regards,
Community Support Team_ Scott Chang

Comments
v-tianyich-msft
Community Support
Status changed to: Delivered

Hi @DennesTorres 

 

It doesn't seem to be able to convert notebook format to .json format. However, you can try to create three project branches for it, Dev,Prod,Master.It also manages the code and provides environment testing as well.

 

Best regards,
Community Support Team_ Scott Chang

DennesTorres
Skilled Sharer

Hi,

 

I think there is a misunderstanding.

 

The idea is not asking to convert the notebook code to json.

 

The idea is asking to not put lakehouse identification metadata together the notebook code. 

 

Remove this metadata from the notebook code and put in a json to allow a flexible movement betwenn environments.

 

The recommendation to create three project branches, dev, test, master, is exactly what doesn't work until this idea is implemented.

 

Test it yourself: create the branches, link each one with a different workspace, each workspace containing a different lakehouse and check what happens with the notebooks when you move them across the branches using pull requests.

 

Kind Regards,

 

Dennes

 

This is not delivered at all.