Deployment Pipeline for OneLake

Hi grdelgado, 

What storage mode are you using for your semantic models? 
Import, DirectQuery, and DirectLake on SQL connections can all be remapped with deployment pipelines. DirectLake on OneLake cannot yet. 

If you're using DirectLake on OneLake, you can use the python ci-cd library to remap the connections, or you can do it manually in VS Code with Fabric Studio.  

As far as lakehouses, it is intentional that the deployment pipelines do not copy over data. Imagine mixing your DEV data into PRD, that's a recipe for disaster. 

I build all of my notebooks so that they are idempotent, meaning they will always produce the same output regardless of how or when they are run. All of my notebooks have a check to see if their target tables exist, and if not, they will create them. Once I deploy them to a new workspace (from dev to tst, or tst to prod), all I need to do is run them and all the tables that need to exist will be created during that first run.