Forum Discussion
Issue with Deployment movement from QA to Prod
Hello JacobJoo
The challenges you’re encountering with deployment on Fabric are quite typical. While your current approach is effective, it does involve additional manual effort.
I suggest implementing GIT integration for your workspaces, with only the Dev environment set to writable and QA and Prod configured as read-only from their respective GIT branches.
Additionally, be sure to parameterise all environment-specific variables and references, such as Lakehouse names, Warehouses, and SQL endpoints.
For promoting to higher environments, it is preferable to use Pull Requests rather than deployment pipelines.
Hi JacobJoo ,
There are two ways you can approach here.
1. Deployment pipelines.
As you mentioned you have atleast 20 pipelines which might grow later, you can still use the pipeline by selectung the master pipeline and then selecting the related items button. This should select all other pipelines related to it. We have tried this method when we need to move/copy pipelines from one to another workspace.
2. Git.
Most standard method is to use Git integration only. Have different branches for both workspaces and follow the regular git process. Although there is no staging here we need to commit directly. So first commit, then get it approved then push it another higher env and at last sync the higher env workspace.
If you need quick fix and need to move items/artifacts in linear fashion , deployment pipeline still works. But it not track who is done what and when. It is the limation which comes by Deployment pipelines. Otherwise use git integration. It is most efficeint way till now.
Hope this helps. Let me know if you have any doubt, we can discuss.