Hi @dpiech10
As of now, the deployment pipeline does not fully support copying the content of Lakehouses, such as tables and files, to the destination workspace. This means that while the structure of the lakehouses and warehouses is copied, the actual data and content are not automatically transferred.
Here is a similar thread for your reference: Deployment pipeline and lakehouse content - Microsoft Fabric Community
My understanding is that the data used tends to be different at different stages. For example, development stage uses a small amount of sample data. Testing stage uses test data which simulates production data. And production stage uses real data. Therefore, the current deployment is mainly focused on metadata such as the schema of the object, structure, definition etc., rather than moving all the actual data and files contained within them.
From the Lakehouse in deployment pipelines document, a new empty Lakehouse object with same name is created in the target workspace after the first deployment.
Then to handle the data and files, you can use data pipelines, notebooks, or manual processes to ensure that the target environment has the necessary content.
Additionally, engineers are working on improve the deployment pipeline experience in Fabric. Below is a new feature on the Roadmap.
Lakehouse Shortcuts metadata on git and deployment pipelines
You can also vote up or raise new ideas on Fabric's Idea forum. Below are some ideas about features you might want:
Microsoft Idea: Add Tables or shortcuts to Lakehouse Pipeline deployments in Fabric
Microsoft Idea: lakehouse views not synced between worspaces via deployment pipelines
Microsoft Idea: Reflect Metadata of Warehouse/Lakehouse in Deployment Pipeline
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
