Forum Discussion
Impactful Individualcan a task flow be deployed and versioned?
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.
Impactful Individualthx amy, i'm referring to what ive traditionally called etl. i know its old technology but i could always version an ssis package which is often and end to end source, transform, landing collection of "things".
Community SupportHi 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.
- v-aatheeque
Hi db042190
We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.
- v-aatheeque
Hi db042190
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.