Forum Discussion
Copy job, Lakehouse changing ids causing code to break.
I am working on my feature branch using a copyjob to push data from a remote SQL into a lakehouse. Once I merge my code to the main branch and open the production workspace the copyjob is broke, ...
We maintain a table of workspace/lakehouse ids by name and environment and look these up at pipeline run time.
You can automate the creation of this table using sempy-labs, the API, and/or notebookutils.lakehouse.get.
Technically you could also dynamically look these up in a notebook that is ran before any other job that outputs in its exitValue the list of lakehouses and ids.