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.

tayloramy's avatar
tayloramy
Icon for Super User rankSuper User
2 months ago

Hi db042190​,

I assume you are talking about translytical task flows (AKA User Defined Functions)? 

If so, then you can migrate the UDF object to another workspace with deployment pipelines, however the migration is not exactly smooth yet. 

The UDF itself will be migrated, but you still need to manually edit the report to point it to the new UDF, migrating the report will leave it pointed at the old UDF. 

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

thx 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". 

  • v-aatheeque's avatar
    v-aatheeque
    Icon for Community Support rankCommunity Support
    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.

    • v-aatheeque's avatar
      v-aatheeque
      Icon for Community Support rankCommunity Support
      2 months ago

      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's avatar
        v-aatheeque
        Icon for Community Support rankCommunity Support
        2 months ago

        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.