Forum Discussion
Deployment pipeline - data caching
Hi CarlBlunck,
Items that are supported by the deployment pipelines can all be moved at the same time. See the documentation for supported items: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/intro-to-deployment-pipelines?tabs=new-ui
Also see this great blog post: https://discoveringallthingsanalytics.com/fabric-deployment-pipelines-guide-dynamic-warehouse-connections-in-microsoft-fabric-pipelines/
If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution.
Yes. If you have a dataflow gen2 in say the dev stage, that is reading and writing to a lakehouse in the same stage (in this example dev), and you deploy it to test stage. The dataflow in the test stage will still be reading and writing to the lakehouse in the dev stage. You will have to manually modify the dataflow in the test stage to read/write to the lakehouse in the test stage.
One thing to note, in the target stage, you will need to rebind the dataflow to the lakehouse in the target stage as it will still be pointing to the lakehouse in the source stage. It is kind of the pain, and one of the things still lacking in the CI/CD process for dataflows.
Yes. If you have a dataflow gen2 in say the dev stage, that is reading and writing to a lakehouse in the same stage (in this example dev), and you deploy it to test stage. The dataflow in the test stage will still be reading and writing to the lakehouse in the dev stage. You will have to manually modify the dataflow in the test stage to read/write to the lakehouse in the test stage.