Forum Discussion

db042190's avatar
db042190
Icon for Impactful Individual rankImpactful Individual
2 months ago
Solved

can a task flow be deployed and versioned?

partly assisted by a course and previous post, we are getting our feet wet in this technology.   amy and the other contributors at that post have made us feel a lot more comfortable.  we went to set...
Need Help
  • v-aatheeque's avatar
    v-aatheeque
    2 months ago

    Hi db042190​ 

    In Fabric, the CI/CD model is primarily item-based. Supported artifacts such as Data Pipelines, Dataflows Gen2, Notebooks, Lakehouses, Warehouses, etc. can be versioned through Git and/or promoted using Deployment Pipelines, but they remain separate Fabric items rather than one SSIS-style package.

    You can still design the solution across Dev → Test → Prod workspaces and promote the individual supported artifacts. However, the relationships/dependencies between those artifacts are not currently packaged into a single deployable ETL unit in the same way an SSIS package does.

db042190's avatar
db042190
Icon for Impactful Individual rankImpactful Individual
2 months ago

thx shivekmaharaj, i think you are saying that the underlying pieces like gen2 , lakehouse landing for bronze etc be versioned separately, not as a collection of related sources, destinations, transforms?  im probabluy missing something. 

ShivekMaharaj's avatar
ShivekMaharaj
Icon for Community Champion rankCommunity Champion
2 months ago

Hi db042190​,

Yes, that's basically what I meant, but with one nuance: the underlying Fabric items are versioned individually, but they do not have to be managed as unrelated pieces.

For example, your Dataflow Gen2, Bronze Lakehouse, notebooks/pipelines and downstream Warehouse can all live in the same workspace and Git branch and be promoted together through a deployment pipeline. Fabric's deployment process also handles many item dependencies through autobinding, and you can select related items when promoting a solution.

What Fabric does not currently give you is one SSIS-style package that represents the whole source → transform → destination solution as a single versioned artifact. Git versions the individual Fabric item definitions.

I would therefore think of it as individually versioned items that collectively make up the solution.

The workspace Task Flow is useful as the architectural map over those items, but it is not currently the CI/CD container itself. Microsoft documents that when you export a Task Flow, the JSON preserves the tasks and connectors but not the Fabric item associations.

So for your medallion example, I would keep the related items together in the same solution/workspace/repository, version the supported items through Git, and use the Task Flow to communicate how those pieces fit together.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.