Status:
New
Enable Configurable Deployment Order for Initial Sync from Repo to Workspace in Microsoft Fabric
Issue Summary:
Fabric pipelines cannot be deployed in a specific order, leading to dependency conflicts. This requires manual intervention to ensure pipelines correctly reference each other.
Recommended Workaround:
- Temporarily rename all .platform files for pipelines with dependencies to platform to prevent automatic sync and deployment.
- Deploy pipelines sequentially, ensuring dependencies are deployed first.
- For the pipeline you're deploying:
- Rename its corresponding platform file back to .platform.
- Update the pipeline-content.json file to use the correct pipeline ID of its dependency (retrievable from the URL in Fabric).
- Select Update to sync the pipeline from the repository to Fabric.
- Delete the existing pipeline folder from the repository to avoid conflicts.
- Commit the updated pipeline from Fabric to the repository, choosing Keep current content.
(Note: This process works even if the pipeline ID in the .platform file remains outdated.)
4 Comments
- echaintreau
Advocate II
I completely agree on this udpate it need to be done, we can not work with this sync that failed on regular basis - This issue seems to be true across multiple toolchains - Git Sync as well as Deployment Pipelines (and possibly others). Also make sure that it behaves the same way whether triggered from Fabric UI, REST API, etc.
- ProdwareSaM
Advocate I
Suggestion File in git Folder:
.deployment
Content:
MyLH1.Warehouse/.platform
--MyLH2.Warehouse/.platform -- skip because of Issue #23
MyLH2.Warehouse/.platform -- must be deployed before MyWH
MyNotebook1/.platform
MyPipeline1/.platform
MyWH.Warehouse/.platform
MyNotebook3..platform
MySemanticModel/.platform
MyReport/.platform
<SkipOther>consider:
- what do do with artifacts not specified in the File
- respect comments -- and block quote /* */ and #
- allow Commands to either Skips Other Artefacts or deploy other artefacts in standard order
Additional Idea Post Deployment Tasks, e.g.
- Replace Adjust Connections
- Run MyNotebook1.platform with parameters 1,2,3
- Run MyPipeline1.platform with parameters 1,2,3
- Process MySemanticModel/.platform
if you need to decide then Run MyPipeline1.platform would have highest benefit as you can Run Notebooks and Process MySemanticModel with that.
- ProdwareSaMPS: This Deployment Order should be respected by git sync and fabric deployment pipelines
