Improve check-out process of git repos that have a Warehouse with dependencies on a Lakehouse in the same workspace

In a single Fabric workspace, we have a Silver layer Warehouse with views that reference delta tables within a Bronze layer Lakehouse. We have committed our workspace objects in an Azure DevOps repo. We are not able to clone this repo in the Fabric UI to a new workspace since the Warehouse views try and fail to reference Lakehouse tables, and the Lakehouse tables have not been created yet as part of the checkout process. Therefore, the entire checkout process fails with no clear workaround, as we are not able to run a notebook to create the Lakehouse tables initially as part of the checkout process.

Ideally the Lakehouse table schema would be created first by Fabric, then any Warehouse views that depend on the Lakehouse could be created.

We're getting "invalid object name" errors on the git sync process, for example:

Request ID f929655c-d0ce-bba3-5eb6-8f60f9453f28

Workload Error Code DmsImportDatabaseException

Workload Error Message Error occured during import database for the Datawarehouse '93dcbf41-b028-4754-9c66-6061cb2528a8@f6d7b82f-62c4-489e-b428-4f7b61184318'. File: dbo/Views/CRC_Agency.sql, Error: Invalid object name 'Bronze.dbo.CRC_DEV_DATA_NEW'.